-
Bug
-
Resolution: Not A Defect
-
Major
-
None
-
CentOS, Tomcat container.
We have a job that has the Execute Build Concurrently enabled and is triggered by git pushes. The build time varies depending on the changes that were made. So one run could take 20 minutes, while the next one takes 10.
The problem is when a long running build is triggered and then a fast one after that. The fast one finishes, then waits for the slow one before triggering all the post-build actions or releasing the executor.
See the following thread dump from the master node: http://pastie.org/private/ie4vqghl4tc1g8giifpqq
This is a "major" issue for us because there is no work around that we can find, and it is preventing our build pipeline to complete, delaying the final results of the build.
[JENKINS-16220] With Concurrent Builds enabled, faster builds won't fully complete until slower builds are done.
The behavior you're seeing is deliberate by the configured post-build steps. For a long time, email sending (both Mailer and email-ext IIRC) blocked build completion because it wanted to make sure to use the correct subject ("Failed" vs. "Still Failing"). AFAIK this was changed, leading to potentially slightly wrong email subjects.
Unless the post-build steps are provided by core (and actually have no reason to wait), this is not a core bug, and more information on the job configuration is needed to investigate further. Separate issues should be filed against the responsible post-build action plugins so their authors can investigate further. Some post-build actions may well need this synchronization, while for others, it provides less value than faster build completion.
Please also note: Jenkins "pretends" that the build is complete, meaning, it shows the solid blue orb on the job. Only if you look at the executor list on the left side or look at the console and see the spinner icon do you see that it's still actually running.