|
||||||||
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)
Sergey, do you mean 'artifact archiving' or 'JUnit result archiving'. In the former case, you would be probably right, but I've seen no comment here that artifact archiving is blocking, too.
In the case of JUnit: yes it MUST block to calculate the diff (regressions et.al.) to the previous test results. So it is a feature.