Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-9913

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

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • core
    • RedHat Enterprise Linux 4.8, Jenkins 1.414

    Description

      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.

      Attachments

        Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-6854 Latest compiler warning plugin fails and locks executor.

          • Major - Major loss of function.
          • Open
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-10234 Junit result archiver getting stuck for a long time in concurrent builds

          • Blocker - Blocks development and/or testing work, production could not run.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-21246 email-ext serialises concurrent builds waiting for checkpoint

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-16376 BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE?

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-19820 Claim plugin serializes concurrent builds

          • Major - Major loss of function.
          • Reopened

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-20867 Sending mail blocks on prior build

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-20704 Jenkins Text Finder is waiting for a checkpoint

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-42727 Cppcheck plugin waiting for checkpoint erroneously when concurrent builds are enabled

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-26892 With concurrent builds, IRC Notification blocks later builds from finishing first

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-24450 JacocoPublisher serializes concurrent builds waiting for checkpoint

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-33238 GitPlugin | Concurrent builds are serialized when publishing

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-41005 Violations plugin makes concurrent builds wait

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-43658 Concurrent builds are serialized when publishing

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-20029 BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE?

          • Major - Major loss of function.
          • Closed

          Activity

            People

              jglick Jesse Glick
              pomvr Philip Metting van Rijn
              Votes:
              19 Vote for this issue
              Watchers:
              34 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: