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

Unreserve doesn't set environment variable

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • None
    • lockable-resources 2.3

    Description

      The manual reserve feature doesn't work well with the pipeline variable feature. When a user unreserves a resource and the plugin assigns the resource immediately to a queued build, the environment variable won't be correctly set.

      In LockableResourceManager.unreserve, there is a LockStepExecution.proceed call at the end with the variable left null. I have no idea how to retrieve a singular variable to use at this point in the code. 

      Attachments

        Issue Links

          Activity

            People

              tgr Tobias Gruetzmacher
              stevenfoster Steven Foster
              Votes:
              5 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: