|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
In some ways I would categorize this as a bug, not a new feature.
It limits the functionality, but more importantly - post-build actions that want to deal with downstream jobs executed by the multijob aren't as useful because they may get kicked off while some of the downstream jobs are running.
One way to replicate: create a multijob project that runs three jobs.
phase1:
example1 job shell command: sleep 30 ; true
example2 job shell command: sleep 30 ; true
example3 job shell command: false
Any post-build actions on the multijob happen when example1 and example2 are running.
Here is what I would like to do:
Multijob Project with many phases:
If any of the phase 2 tests fail, multijob exits and phase Z cleanup never happens.
There are workarounds (post build trigger that always runs and monitors running jobs, blocking until they are done which then does the real post-build actions)
I suggest two checkboxes for each multijob phases:
"block until all jobs in this phase are complete"
"continue to next phase even if this phase fails" (default, do not continue)