|
||||||||||||||
|
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.
Jira is not a support site. Ask questions on the jenkinsci-users list instead of claiming everything you don't understand is a critical bug in the software.
Jenkins seems to assign both job runs at the same time to the node in question, while no run has yet assigned the new label in its script execution. But even if that's not the case, Jenkins generally doesn't support use of labels like this, as there's caching going on in the background. Use something better suited for this, e.g. https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin