|
||||||||
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)
For that you can e.g. use the xunit plugin as mentioned in JENKINS-10234.
Generally, don't use any build steps which require blocking behaviour. Yes, very unfortunately it's not visible for end users which build steps do and which don't.