-
New Feature
-
Resolution: Unresolved
-
Major
-
None
We would like to kick off multiple test jobs as build steps, and block waiting for them all to finish. Currently the execute serially. But we have lots of available resources to run them, so it would be so nice to run them in parallel, and get the results in 1 hour, rather than many.
[JENKINS-12480] Build step that runs multiple jobs in parallel, and blocks until all are complete
giuliano carlini
created issue -
Jacobo Jimenez
added a comment - I have this situation configured but it doesnt works fine, maybe this is a kind of incompatibility between plugins:
I use "Parameterized Trigger" + "Run condition" + "Conditional build step" plugins to set a diamond execution but making the number of build in 2nd step variable (even 0) depending on the input parameters.
-One problem is that with 0 value "Counter parameter factory" crash (Java exception) so I use conditional build step to check it. By now that is working as intended but it would be nice Counter parameter factory not to crash with 0 repetitions.
-The main problem is when I launch another build it finish its main step but when it should continue to the 2nd step of the diamond it keeps waiting the downstreams builds of the other execution avoiding users to run more than 1 project at a time.
Jacobo Jimenez
added a comment - I have this situation configured but it doesnt works fine, maybe this is a kind of incompatibility between plugins:
I use "Parameterized Trigger" + "Run condition" + "Conditional build step" plugins to set a diamond execution but making the number of build in 2nd step variable (even 0) depending on the input parameters.
-One problem is that with 0 value "Counter parameter factory" crash (Java exception) so I use conditional build step to check it. By now that is working as intended but it would be nice Counter parameter factory not to crash with 0 repetitions.
-The main problem is when I launch another build it finish its main step but when it should continue to the 2nd step of the diamond it keeps waiting the downstreams builds of the other execution avoiding users to run more than 1 project at a time. 
Greg Temchenko
added a comment - I've got the same troubles recently.
We also use ""Parameterized Trigger" + "Run condition" + "Conditional build step"", but I tried to disable run-condition and conditional-buildstep, but the problem still persists.
Jacob, did you try to disable plugins?
Also I use 1.464 and I tried to downgrade to 1.460.
Greg Temchenko
added a comment - I've got the same troubles recently.
We also use ""Parameterized Trigger" + "Run condition" + "Conditional build step"", but I tried to disable run-condition and conditional-buildstep, but the problem still persists.
Jacob, did you try to disable plugins?
Also I use 1.464 and I tried to downgrade to 1.460. 
Mishael Kim
added a comment - I believe this is a bug in the current release (2.15 and 2.16) of the Parameterized Trigger Plugin. I've downgraded to version 2.10 and it is working again properly.
The trick is to create only 1 build step, and then nest all of the triggers under that one build step so that they can all run in parallel.
Mishael Kim
added a comment - I believe this is a bug in the current release (2.15 and 2.16) of the Parameterized Trigger Plugin. I've downgraded to version 2.10 and it is working again properly.
The trick is to create only 1 build step, and then nest all of the triggers under that one build step so that they can all run in parallel. Mishael Kim
made changes -
| Affects Version/s | New: current [ 10162 ] | |
| Issue Type | Original: Improvement [ 4 ] | New: Bug [ 1 ] |
Alexander Boyd
added a comment - Seeing this in 2.16. I'll try downgrading tomorrow and see if I can spot which version it first occurred in.
Alexander Boyd
added a comment - Seeing this in 2.16. I'll try downgrading tomorrow and see if I can spot which version it first occurred in. Alexander Boyd
added a comment - 2.12 is the earliest version in which this works. It broke in 2.13 and started running all jobs serially, even if they're located in the same build step.
Alexander Boyd
added a comment - 2.12 is the earliest version in which this works . It broke in 2.13 and started running all jobs serially, even if they're located in the same build step. 
Gardner Bickford
added a comment - Hi everyone. I registered this issue in the "kickstarting" section on FreedomSponsors. This means that if you need this issue that bad, you can go to http://www.freedomsponsors.org/core/issue/80/build-step-that-runs-multiple-jobs-in-parallel-and-blocks-until-all-are-complete and offer a few bucks for it.
Gardner Bickford
added a comment - Hi everyone. I registered this issue in the "kickstarting" section on FreedomSponsors. This means that if you need this issue that bad, you can go to http://www.freedomsponsors.org/core/issue/80/build-step-that-runs-multiple-jobs-in-parallel-and-blocks-until-all-are-complete and offer a few bucks for it. Currently, one can run parallel jobs when specifying them in a single build step/"Projects to build". But this requires them to have the same parameters (except factory ones).
But when specifying multiple "Projects to build" within a single build step, there's no option "Block until the triggered projects finish their builds" that would wait for all jobs of this build step.
I'll be trying "File Generator Parameter Factory" now.... Doesn't work for me, because in many cases I need to run different jobs.
Marko Macek
added a comment - - edited Currently, one can run parallel jobs when specifying them in a single build step/"Projects to build". But this requires them to have the same parameters (except factory ones).
But when specifying multiple "Projects to build" within a single build step, there's no option "Block until the triggered projects finish their builds" that would wait for all jobs of this build step.
I'll be trying "File Generator Parameter Factory" now.... Doesn't work for me, because in many cases I need to run different jobs.
You can do this already - just specify a list of jobs to build in one step.