|
||||||||||||
|
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.
I've been able to reproduce this issue on a test instance of 1.600 only when env-inject is installed and enabled. Disable it, restart, issue is gone. Enable it, restart, issue is back.
It seems to occur when two builds (different projects but same config, only the sleep + echo shell step) run in parallel (on the master node for me). There's a solid chance that one of the two (never both so far) fails.
Presumably related to
JENKINS-26755so tentatively assigning to Nicolas De Loof. Given how popular this plugin is this can easily blow up a lot of instances, especially assuming that users who care about Jenkins security upgrade earlier than usual due to the security advisory.If anyone's interested and capable, it should be easy enough to revert the changes for
JENKINS-26755and create a build of 1.600 without it to see whether it resolves the issue for you. I could also provide such a build if you're willing to trust some random guy on the internet. Just respond here.