[JIRA] [jenkins-multijob-plugin] (JENKINS-23161) Aborted or failed job in a phase does not immediately cause the multi-job to fail
Mathieu Cantin commented on JENKINS-23161 Aborted or failed job in a phase does not immediately cause the multi-job to fail Yes, I have submit a pull request to fix this bug. 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/d/optout.
[JIRA] [jenkins-multijob-plugin] (JENKINS-23161) Aborted or failed job in a phase does not immediately cause the multi-job to fail
James Levinson commented on JENKINS-23161 Aborted or failed job in a phase does not immediately cause the multi-job to fail The killPhaseOn, introduced in 1.11, defaults to Failure, as indicated in your screenshot, so this should fail the phase after any job failure and abort the other running jobs. On my systems, I have observed this does in fact work. I am now on plugin version 1.13. I would also argue that the developers changed the behavior of the plugin when they selected Failure as a default and it should have been set to Never. 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/d/optout.
[JIRA] [jenkins-multijob-plugin] (JENKINS-23161) Aborted or failed job in a phase does not immediately cause the multi-job to fail
Mathieu Cantin assigned JENKINS-23161 to Mathieu Cantin Aborted or failed job in a phase does not immediately cause the multi-job to fail Change By: Mathieu Cantin (10/Sep/14 3:50 PM) Assignee: MathieuCantin 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/d/optout.
[JIRA] [jenkins-multijob-plugin] (JENKINS-23161) Aborted or failed job in a phase does not immediately cause the multi-job to fail
Hilton Campbell created JENKINS-23161 Aborted or failed job in a phase does not immediately cause the multi-job to fail Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Screen Shot 2014-05-22 at 3.45.49 PM.png Components: jenkins-multijob-plugin Created: 22/May/14 9:47 PM Description: I have a MultiJob with a single phase consisting of 3 child jobs. When any one of these child jobs fails (or is aborted) I would expect the MultiJob to fail and cancel all the other child jobs immediately. Instead, it waits until all child jobs complete before failing. I've attached a screenshot of my configuration. Am I doing it wrong, or is there a bug? Project: Jenkins Priority: Major Reporter: Hilton Campbell 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/d/optout.
