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

Aborted build with concurrency=1 blocks new build

    Details

    • Similar Issues:

      Description

      When a workflow stage reached its max number of concurrencies, and a build is aborted, this is not registered as finished builld/stage

      Steps to reproduce:
      1. Create a build with one stage and concurrency=1
      2. STart the build
      3. Abort build when stage started, but before stage is finished
      4. Restart a build

      The new build will tell you it is waiting for the build (that was just aborted) to finish. Wven deleting the build won't make any difference.

      Workaround: increment the number of concurrent builds'

      Maybe similar to: https://issues.jenkins-ci.org/browse/JENKINS-26709

        Attachments

          Activity

          Hide
          maxfields2000 Maxfield Stewart added a comment -

          Can confirm I ran into this myself. It doesn't happen every time for me but it has definitely happened. If you follow the linked issue you can find the work around but I'd love a more abvious way to kill that "zombie" build.

          Show
          maxfields2000 Maxfield Stewart added a comment - Can confirm I ran into this myself. It doesn't happen every time for me but it has definitely happened. If you follow the linked issue you can find the work around but I'd love a more abvious way to kill that "zombie" build.
          Hide
          jglick Jesse Glick added a comment -

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

          Show
          jglick Jesse Glick added a comment - Probably will not fix, as we plan to deprecate concurrency-related features of stage .
          Hide
          larsmeynberg Lars Meynberg added a comment -

          Jesse Glick Any hints about how to handle concurrency stuff for e.g. server deployments then?

          Show
          larsmeynberg Lars Meynberg added a comment - Jesse Glick Any hints about how to handle concurrency stuff for e.g. server deployments then?
          Hide
          jglick Jesse Glick added a comment -

          Use lock from the Lockable Resources plugin.

          Show
          jglick Jesse Glick added a comment - Use lock from the Lockable Resources plugin.
          Hide
          abayer Andrew Bayer added a comment -

          Closing as won't fix since concurrency on stage has been deprecated for over a year now.

          Show
          abayer Andrew Bayer added a comment - Closing as won't fix since concurrency on stage has been deprecated for over a year now.

            People

            • Assignee:
              jglick Jesse Glick
              Reporter:
              hwdegroot Rik de Groot
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: