[
https://issues.jenkins-ci.org/browse/JENKINS-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160608#comment-160608
]
Laura Neff commented on JENKINS-9913:
-------------------------------------
I saw this also this evening. I use the throttle concurrent builds plugin and
had four instances of the same parameterized job running. The three that
finished weren't released and hogged their executors until the fourth and last
finished. Postbuild actions for all were: archive artifacts, Groovy postbuild
script, fingerprint a file, set build description, and build other projects
(extended) where the trigger was not satisfied, send email. No Junit tests.
Jenkins 1.428, running on Windows 7, and the jobs in question were all running
on the master.
Throttle Concurrent Builds plugin v. 1.6
> Concurrent builds getting batched/nodes not getting released when jobs are
> completed
> ------------------------------------------------------------------------------------
>
> Key: JENKINS-9913
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9913
> Project: Jenkins
> Issue Type: Bug
> Components: concurrent-build
> Affects Versions: current
> Environment: RedHat Enterprise Linux 4.8, Jenkins 1.414
> Reporter: Philip Metting van Rijn
> Assignee: Kohsuke Kawaguchi
>
> We're experiencing an issue with concurrent builds where Jenkins appears to
> be associating separate builds (run on different machines) such that they
> won't be marked as completed until all jobs are completed. For example, if
> we kick off 5 concurrent builds on 5 different nodes, builds 1-4 won't be
> marked as completed if build #5 is still running, even though builds 1-4 are
> finished. I've seen a report of someone experiencing this issue elsewhere:
> http://groups.google.com/group/jenkinsci-users/browse_thread/thread/e477e25910266d2a?fwc=1
> but a solution wasn't posted. We do not have the batch plugin or the locks
> and latches plugin installed. We've disabled all post-build processing and
> switched between different containers (Glassfish/Tomcat), but the problem
> persists. I couldn't find an issue logged for this other than the
> aforementioned posting.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
