We found that this is probably the cause of our problem, but it was really hard to determine: https://issues.jenkins-ci.org/browse/JENKINS-19820
Description When executing builds in parallel*, some post-build actions force the builds to end in the same order they were started. Even if build #2 is ready, it has to wait until build #1 is done. Claim plugin is one such plugin that serializes build order. -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Build-Flow-Plugin-Multiple-concurrent-jobs-are-ended-in-sequence-tp4680317p4681312.html Sent from the Jenkins users mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
