|
||||||||
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 builds getting batched/nodes not getting released when jobs are completed
m.a.lewi...@gmail.com (JIRA) Mon, 05 Nov 2012 14:05:45 -0800
- [JIRA] (JENKINS-9913) Concurrent build... m.a.lewi...@gmail.com (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... cyrille.boulan...@atmel.com (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... stephane.mainch...@gmail.com (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... svs1...@gmail.com (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... xavier.leprev...@atmel.com (JIRA)
A very unfortunate bug indeed, especially if one of the batch of jobs getting launched gets stuck for whatever reasons (remote execution over ssh, etc.). The stuck job will cause the whole batch to get stuck, and the possibility of this happening is exactly why we're using concurrent executions in first place...