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

Locked resources not freed up by Pipeline job hard kill

XMLWordPrintable

      Since LockStepExecution.Callback.finished(context) never gets called in the case of a hard kill, resources can be locked forever when a build is hard killed. It's possible to manually unlock those resources from the UI, but it'd be preferable to have some behavior that detects this scenario and is able to unlock resources locked by defunct builds.

          [JENKINS-36479] Locked resources not freed up by Pipeline job hard kill

          Andrew Bayer created issue -
          Andrew Bayer made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-28183 [ JENKINS-28183 ]
          Jesse Glick made changes -
          Labels New: robustness workflow
          Andrew Bayer made changes -
          Remote Link New: This issue links to "PR #34 (Web Link)" [ 14589 ]
          Andrew Bayer made changes -
          Remote Link New: This issue links to "PR #35 (Web Link)" [ 14590 ]
          Andrew Bayer made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 173189 ] New: JNJira + In-Review [ 199408 ]
          Andrew Bayer made changes -
          Labels Original: robustness workflow New: pipeline robustness workflow
          Andrew Bayer made changes -
          Labels Original: pipeline robustness workflow New: pipeline robustness
          Denys Digtiar made changes -
          Link New: This issue is related to JENKINS-40368 [ JENKINS-40368 ]

            abayer Andrew Bayer
            abayer Andrew Bayer
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: