|
||||||||
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... 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)
- [JIRA] (JENKINS-9913) Concurrent ... in...@vaultive.com (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... ku...@gmx.de (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... svs1...@gmail.com (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... ku...@gmx.de (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... svs1...@gmail.com (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... ku...@gmx.de (JIRA)
There are several cause described here. Some are JUnit archiving, which is specifically handled in JENKINS-10234. Some seem to be related to email notification.
I dare to say that in almost all cases this is a feature and not a bug as the logic for email notification and JUnit result archiving needs to wait until the previous builds are finished.