|
||||||||||||
|
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.
Adding the stage step is certainly not required. If it seems to fix the problem in your case, it was really something else you did.
https://github.com/jenkinsci/workflow-plugin/commit/1c0b425c950892f2fdce18553726cb5f2d7a7a86 was supposed to have fixed this kind of error. But I can still reproduce it if I install the Workflow plugins without restarting Jenkins. After the restart it is fine. I think this is because the recording of the master channel happens during Jenkins startup, not thereafter.
I will see if I can mark these plugins as requiring a restart of Jenkins. Alternately, the code to look up the computer for a channel may need to fall back to searching connected computers in case the listener trick failed.