|
||||||||
|
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... [email protected] (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... [email protected] (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... [email protected] (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... [email protected] (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... [email protected] (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... [email protected] (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... [email protected] (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... [email protected] (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... [email protected] (JIRA)
- [JIRA] (JENKINS-9913) Concurrent ... [email protected] (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.