[JIRA] (JENKINS-54514) Document parallel step failure logic
Title: Message Title Jesse Glick assigned an issue to Craig Ringer Jenkins / JENKINS-54514 Document parallel step failure logic Change By: Jesse Glick Assignee: Craig Ringer Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54514) Document parallel step failure logic
Title: Message Title Jesse Glick started work on JENKINS-54514 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54514) Document parallel step failure logic
Title: Message Title Jesse Glick updated JENKINS-54514 Jenkins / JENKINS-54514 Document parallel step failure logic Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54514) Document parallel step failure logic
Title: Message Title Craig Ringer updated an issue Jenkins / JENKINS-54514 Document parallel step failure logic Change By: Craig Ringer The documentation for the parallel pipeline step is excessively brief. This pull request addresses that by documenting:* What the criteria for failure and success are* The (lack of) meaning of the closure return value* Why some failures are "silent" in that they report no exception (hudson.AbortException)* How to get results out of the branches if desired* "Failed in branch" message* A short practical example* The return value of the parallel step, and why it should be ignored per JENKINS-26033 See https://github.com/jenkinsci/workflow-cps-plugin/pull/260 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54514) Document parallel step failure logic
Title: Message Title Craig Ringer created an issue Jenkins / JENKINS-54514 Document parallel step failure logic Issue Type: Patch Assignee: Unassigned Components: workflow-cps-plugin Created: 2018-11-07 13:38 Environment: Jenkins ver. 2.138.2 ; workflow-cps-plugin 2.6 Priority: Minor Reporter: Craig Ringer The documentation for the parallel pipeline step is excessively brief. This pull request addresses that by documenting: What the criteria for failure and success are The (lack of) meaning of the closure return value Why some failures are "silent" in that they report no exception (hudson.AbortException) How to get results out of the branches if desired "Failed in branch" message A short practical example The return value of the parallel step, and why it should be ignored per JENKINS-26033
