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

A stage with concurrency: 0 creates a zombie workflow.

      Steps to reproduce :
      Create a workflow.
      Add a stage with a concurrency of 0.

      Expected :

      • Either the concurrency value is rejected on saving,
      • Or the stage actually has no concurrency constraints (this what I expected when I hit this).

      Actual :
      The workflow is blocked with the message "Waiting for builds []".
      When it reaches this point, the workflow cannot be aborted, ever.
      The log states "Aborted by whoever" each time someone tries to abort the build, but the workflow is still blocked.
      It is still blocked even after a Jenkins restart.

          [JENKINS-26709] A stage with concurrency: 0 creates a zombie workflow.

          Jesse Glick added a comment -

          JENKINS-25550 describes how to delete the bad build as a workaround.

          Jesse Glick added a comment - JENKINS-25550 describes how to delete the bad build as a workaround.

          Robby Pocase added a comment -

          You will need to abort the bad build before running doDelete. Otherwise, the bad build will get stuck in a running state and cannot be removed.

          Robby Pocase added a comment - You will need to abort the bad build before running doDelete. Otherwise, the bad build will get stuck in a running state and cannot be removed.

          Jesse Glick added a comment -

          Probably will not fix, as we plan to deprecate concurrency-related features of stage.

          Jesse Glick added a comment - Probably will not fix, as we plan to deprecate concurrency-related features of stage .

          Andrew Bayer added a comment -

          Yeah, concurrency is deprecated/dead, so closing as won't fix.

          Andrew Bayer added a comment - Yeah, concurrency is deprecated/dead, so closing as won't fix.

            jglick Jesse Glick
            jblanchard Jean Blanchard
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: