|
||||||||
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 |
- [JIRA] (JENKINS-9688) Build runs on master without ... jos...@java.net (JIRA)
- [JIRA] (JENKINS-9688) Build runs on master wit... jos...@java.net (JIRA)
- [JIRA] (JENKINS-9688) Build runs on master wit... jos...@java.net (JIRA)
After several similar situations in the past weeks like this one where concurrent jobs using the same lock I think the problem may be mostly between chair and keyboard, but also due to lack of informative messages.
Lets assume 3 jobs A, B and C using the same lock, the following timeline occurs:
Also we observed that if we don't Cancel C eventually it starts executing normally when B finishes and showing it has acquired the lock in the log file.
Bottom line the problem is lack of informative messages from the plugin to provide the proper feedback to users so they don't panic.
Workaround: Revoke users permissions to Cancel builds that are using locks.