1
votes

We are using Jenkins and the build-flow plugin to orchestrate some jobs for our deployment. After the build-flow finished, we want to trigger some more jobs as a downstream dependency.

I tried to solve this requirement via a post-build action, where I set up a trigger for parameterized builds on other projects. It should be triggered when the flow is "stable or unstable but not failed", but the build-flow job refuses to trigger any of these downstream jobs although the current build was green and also the last five builds where green, so the build-flow is stable.

Do you have any ideas how to solve this problem or did I just found a bug in the build-flow plugin? Google didn’t show me any helpful results.

2

2 Answers

2
votes

I have exactly the same issue. Jenkins ver. 1.601 with CloudBees Build Flow plugin 0.17

Workaround: enable "Flow run needs a workspace"

Seems as known issue

0
votes

This might be related to a problem I had. The solution was to not filter the run parameter in the configuration of the downstream job.