|
giuliano carlini created JENKINS-12480:
------------------------------------------ Summary: Build step that runs multiple jobs in parallel, and blocks until all are complete Key: JENKINS-12480 URL: https://issues.jenkins-ci.org/browse/JENKINS-12480 Project: Jenkins Issue Type: Improvement Components: parameterized-trigger Reporter: giuliano carlini Assignee: huybrechts 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
[ https://issues.jenkins-ci.org/browse/JENKINS-12480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157998#comment-157998 ] abayer commented on JENKINS-12480: ---------------------------------- You can do this already - just specify a list of jobs to build in one step. > Build step that runs multiple jobs in parallel, and blocks until all are complete > --------------------------------------------------------------------------------- > > Key: JENKINS-12480 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12480 > Project: Jenkins > Issue Type: Improvement > Components: parameterized-trigger > Reporter: giuliano carlini > Assignee: huybrechts > > 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-12480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163060#comment-163060 ] Jacobo Jimenez commented on JENKINS-12480: ------------------------------------------ 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. > Build step that runs multiple jobs in parallel, and blocks until all are complete > --------------------------------------------------------------------------------- > > Key: JENKINS-12480 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12480 > Project: Jenkins > Issue Type: Improvement > Components: parameterized-trigger > Reporter: giuliano carlini > Assignee: huybrechts > > 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-12480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163532#comment-163532 ] Greg Temchenko commented on JENKINS-12480: ------------------------------------------ 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. > Build step that runs multiple jobs in parallel, and blocks until all are complete > --------------------------------------------------------------------------------- > > Key: JENKINS-12480 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12480 > Project: Jenkins > Issue Type: Improvement > Components: parameterized-trigger > Reporter: giuliano carlini > Assignee: huybrechts > > 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
|
|||||||||||
|
In reply to this post by JIRA noreply@jenkins-ci.org
|
|
In reply to this post by JIRA noreply@jenkins-ci.org
|
|||||||||||
|
In reply to this post by JIRA noreply@jenkins-ci.org
|
|||||||||||
|
In reply to this post by JIRA noreply@jenkins-ci.org
|
|||||||||||
| Powered by Nabble | Edit this page |

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.