[JIRA] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
Alvaro ME commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed How is this a feature? I do not use JUnit. I have a gerrit plugin that triggers a (parameterized) build+test job (a build script, and another script that runs some tests, all in a small shell snippet) whenever code is pushed to the repository. When the job is completed (successfully or not), an email notification needs to go out to the authors. It doesn't get much simpler than this. Commits are independent from each other, and as a consequence, so are the build jobs. Why would you want the email plugin to sit in some checkpoint if the job is done? Is there a workaround for this? This causes horrendous problems in our setup: aside from the resource waste (many nodes spend long periods of time waiting for slower builds), bugs in the test code will cause the whole cluster to deadlock. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
Inbar Rose commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed same problem here. total blocker. task A starts, then task B starts. task B reaches the 'Recording test results' stage and hangs until task A finishes. after testing with simple timed builds with many plugins/options enabled/disabled concluded that junit is the problem. - found another issue like this here: https://issues.jenkins-ci.org/browse/JENKINS-10234 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 builds getting batched/nodes not getting released when jobs are completed
Sergey Smirnov commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed It is not a feature. All concurent builds execute in separated workspace and must archive its artifacts independently. No need to wait others builds if current have finished. 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 builds getting batched/nodes not getting released when jobs are completed
kutzi commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed Sergey, do you mean 'artifact archiving' or 'JUnit result archiving'. In the former case, you would be probably right, but I've seen no comment here that artifact archiving is blocking, too. In the case of JUnit: yes it MUST block to calculate the diff (regressions et.al.) to the previous test results. So it is a feature. 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 builds getting batched/nodes not getting released when jobs are completed
Sergey Smirnov commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed I mean all result of concurent job. For example. I have Jenkins job that execute E2E tests on different QA servers. I started 10 jobs. One job running 5 hours. But others takes 1 hour. Then I can't see results of finished job and have to wait 4 hours to see it. We must have instrument to prevent this. 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 builds getting batched/nodes not getting released when jobs are completed
kutzi commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed 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. 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 builds getting batched/nodes not getting released when jobs are completed
Xavier Leprévost commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed It would be nice to know if someone will investigate this problem. 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 builds getting batched/nodes not getting released when jobs are completed
Cyrille Boulanger commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed Bitten by this issue also 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 builds getting batched/nodes not getting released when jobs are completed
Margaret Lewicka commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed A very unfortunate bug indeed, especially if one of the batch of jobs getting launched gets stuck for whatever reasons (remote execution over ssh, etc.). The stuck job will cause the whole batch to get stuck, and the possibility of this happening is exactly why we're using concurrent executions in first place... 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 builds getting batched/nodes not getting released when jobs are completed
Sergey Smirnov commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed Created:08/Jun/11 9:43 PM date Mon Oct 22 16:15:51 MSK 2012 Resolution: Unresolved 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 builds getting batched/nodes not getting released when jobs are completed
Sergey Smirnov updated JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed Change By: Sergey Smirnov (19/Oct/12 6:20 AM) Attachment: jenkins2.jpeg Attachment: jenkins1.jpeg 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 builds getting batched/nodes not getting released when jobs are completed
Sergey Smirnov commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed I attached to screenshot to explain again what's happen. Jobs 537, 538, 539 have finished as you can see on second screenshot. But executors is still busy as you can see on first one. 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 builds getting batched/nodes not getting released when jobs are completed
Xavier Leprévost commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed I there any chance to have this fixed soon ? 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 builds getting batched/nodes not getting released when jobs are completed
lukas rytz commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed This is a very unfortunate bug. I observed today that Jenkins finishes builds in the exact same order as they were started. So if you have builds #1, #2, #3 running, Jenkins will always let #1 finish first, then #2, then #3. It doesn't matter which of the builds finishes its actions first. I wonder if there's an inherent limitation in Jenkins that a build #n cannot be running while #(n+x) has already completed. 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 builds getting batched/nodes not getting released when jobs are completed
lukas rytz edited a comment on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed A short test confirms what Logan Mattox observed: it's due to the e-mail notifications (both with the built-in "E-Mail Notification" post-build action, and the email-ext plugin). Some other post-build actions don't seem to trigger the problem: I tried launching a downstream job, and this allows build #2 to complete before #1. However, the "Jenkins Text Finder" plugin ALSO triggers the problem. Maybe it's related to plugins that read the console output? 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 builds getting batched/nodes not getting released when jobs are completed
lukas rytz commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed A short test confirms what Logan Mattox observed: it's due to the e-mail notifications (both with the built-in "E-Mail Notification" post-build action, and the email-ext plugin). Other post-build actions don't seem to trigger the problem: I tried launching a downstream job, and this allows build #2 to complete before #1. 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 builds getting batched/nodes not getting released when jobs are completed
stephane mainchain commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed Any idea when this will be fixed? this one's a blocker for me. 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 builds getting batched/nodes not getting released when jobs are completed
[ https://issues.jenkins-ci.org/browse/JENKINS-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163332#comment-163332 ] Sergey Smirnov commented on JENKINS-9913: - Do anybody read this ticket? This bug make our work slow. Help! 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
[JIRA] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
[ https://issues.jenkins-ci.org/browse/JENKINS-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163249#comment-163249 ] Sergey Smirnov commented on JENKINS-9913: - Any progress? Latest Jenkins has this bug. 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
[JIRA] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
[ https://issues.jenkins-ci.org/browse/JENKINS-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162659#comment-162659 ] Logan Mattox commented on JENKINS-9913: --- We had a very similar issue, and found the problem to be in the email part of core somewhere. When we disabled all plugins that extended email, and turned off build notification emails, our builds no longer block other concurrent builds that share the same name. The the work around isn't ideal, as we then had to go add email code to several build scripts (that we are trying to simplify and remove maintenance from). 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
[JIRA] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
[ https://issues.jenkins-ci.org/browse/JENKINS-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161781#comment-161781 ] Sergey Smirnov commented on JENKINS-9913: - Any progress in resolve issue? 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
[JIRA] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
[ https://issues.jenkins-ci.org/browse/JENKINS-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161568#comment-161568 ] Sergey Smirnov commented on JENKINS-9913: - Jenkins ver. 1.458 Still have problem: concurrent build not finished while last build ended. 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
[JIRA] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
[ https://issues.jenkins-ci.org/browse/JENKINS-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160675#comment-160675 ] Xavier Leprévost commented on JENKINS-9913: --- I have the same problem. I am using parameterized trigger where the parameters is a SVN branch. I start : - job build 1 from branch1 - job build 2 from branch2 - job build 3 from branch3 - job build 4 from branch4 They are all running fine, but if job 2 or 3 or 4 finish before 1. They are really finish only when job 1 is finish. Then problem is the node resource not available then for starting a new job, and I am waiting the result of the build. 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
[JIRA] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
[ https://issues.jenkins-ci.org/browse/JENKINS-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
