|
||||||||
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-9913) Concurrent build... lukas.r...@epfl.ch (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... lukas.r...@epfl.ch (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... lukas.r...@epfl.ch (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... stephane.mainch...@gmail.com (JIRA)
This is a very unfortunate bug. I observed today that Jenkins finishes builds in the exact same order as they were started. So if you have builds #1, #2, #3 running, Jenkins will always let #1 finish first, then #2, then #3. It doesn't matter which of the builds finishes its actions first.
I wonder if there's an inherent limitation in Jenkins that a build #n cannot be running while #(n+x) has already completed.