Not obvious why some post-build tasks enforce serial behavior even when builds are concurrent

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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.

        1. jenkins1.jpeg
          jenkins1.jpeg
          222 kB
        2. jenkins2.jpeg
          jenkins2.jpeg
          259 kB

            Assignee:
            Jesse Glick
            Reporter:
            Philip Metting van Rijn
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: