|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
This problem happens when a step with a body (such as ExecutorStep) reports a failure to CpsStepContext.onFailure() while the body is still running.
CpsStepContext.onFailure() is probably expected to do something about the running body, but it doesn't do anything, and leaves the body running. The failed node methods returns in CPS code, and that ends up running in parallel with the body as two CpsThread objects.
This breaks the flow graph badly, and in a program like the following, the last node in the flow graph comes as a result of successful completion of the sh step, therefore FlowEndNode will not have any ErrorAction.
node { sh 'sleep 60' }