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

Multiple pipeline instances running concurrently when concurrent execution disabled

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core
    • Jenkins 2.7.1
      Jenkins 2.49
      Pipeline plugin 2.4
    • Jenkins 2.136

      I have configured a Jenkins pipeline to disable concurrent builds:

      properties([
          disableConcurrentBuilds()
      ])
      

      However, I have noticed on some occasions the next 2 builds are pulled from the pipeline's queue and executed concurrently. Why this occurs is not obvious at all.

          [JENKINS-41127] Multiple pipeline instances running concurrently when concurrent execution disabled

          Joe Harte created issue -
          Joe Harte made changes -
          Description Original: I have configured a Jenkins pipeline to disabled concurrent builds:

          {code}
          properties([
              disableConcurrentBuilds()
          ])
          {code}

          However, I have noticed on some occasions multiple instances of the pipeline execute concurrently. This seems to happen when the pipeline is triggered by an upstream job at the same time that a user manually triggers it - possible race condition?
          New: I have configured a Jenkins pipeline to disable concurrent builds:

          {code}
          properties([
              disableConcurrentBuilds()
          ])
          {code}

          However, I have noticed on some occasions multiple instances of the pipeline execute concurrently. This seems to happen when the pipeline is triggered by an upstream job at the same time that a user manually triggers it - possible race condition?
          Joe Harte made changes -
          Description Original: I have configured a Jenkins pipeline to disable concurrent builds:

          {code}
          properties([
              disableConcurrentBuilds()
          ])
          {code}

          However, I have noticed on some occasions multiple instances of the pipeline execute concurrently. This seems to happen when the pipeline is triggered by an upstream job at the same time that a user manually triggers it - possible race condition?
          New: I have configured a Jenkins pipeline to disable concurrent builds:

          {code}
          properties([
              disableConcurrentBuilds()
          ])
          {code}

          However, I have noticed on some occasions multiple instances of the pipeline execute concurrently. This seems to happen when the pipeline is triggered by an upstream job at the same time that a user manually triggers it - possible race condition?

          Will attach logs when this occurs again, don't currently have them available.
          Joe Harte made changes -
          Environment Original: Jenkins 2.7.1
          Pipeline plugin 2.4
          New: Jenkins 2.7.1
          Jenkins 2.49
          Pipeline plugin 2.4
          Jesse Glick made changes -
          Component/s New: workflow-job-plugin [ 21716 ]
          Component/s Original: pipeline [ 21692 ]
          Jesse Glick made changes -
          Labels Original: bug concurrent pipeline New: concurrent
          Joe Harte made changes -
          Component/s New: throttle-concurrent-builds-plugin [ 15745 ]
          Component/s Original: workflow-job-plugin [ 21716 ]
          Joe Harte made changes -
          Component/s New: workflow-job-plugin [ 21716 ]
          Component/s Original: throttle-concurrent-builds-plugin [ 15745 ]
          Joe Harte made changes -
          Description Original: I have configured a Jenkins pipeline to disable concurrent builds:

          {code}
          properties([
              disableConcurrentBuilds()
          ])
          {code}

          However, I have noticed on some occasions multiple instances of the pipeline execute concurrently. This seems to happen when the pipeline is triggered by an upstream job at the same time that a user manually triggers it - possible race condition?

          Will attach logs when this occurs again, don't currently have them available.
          New: I have configured a Jenkins pipeline to disable concurrent builds:

          {code}
          properties([
              disableConcurrentBuilds()
          ])
          {code}

          However, I have noticed on some occasions multiple instances of the pipeline execute concurrently for no apparent reason; the next 2 builds are pulled from the queue and exited at the same time.
          Joe Harte made changes -
          Description Original: I have configured a Jenkins pipeline to disable concurrent builds:

          {code}
          properties([
              disableConcurrentBuilds()
          ])
          {code}

          However, I have noticed on some occasions multiple instances of the pipeline execute concurrently for no apparent reason; the next 2 builds are pulled from the queue and exited at the same time.
          New: I have configured a Jenkins pipeline to disable concurrent builds:

          {code}
          properties([
              disableConcurrentBuilds()
          ])
          {code}

          However, I have noticed on some occasions the next 2 builds are pulled from the pipeline's queue and executed concurrently. Why this occurs is not obvious at all.
          Jesse Glick made changes -
          Priority Original: Major [ 3 ] New: Critical [ 2 ]

            dnusbaum Devin Nusbaum
            boon Joe Harte
            Votes:
            3 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: