With Concurrent Builds enabled, faster builds won't fully complete until slower builds are done.

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

XMLWordPrintable

    • Type: Bug
    • Resolution: Not A Defect
    • Priority: Major
    • Component/s: core
    • Environment:
      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.

            Assignee:
            Kohsuke Kawaguchi
            Reporter:
            Joel Johnson
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: