Unreserve doesn't set environment variable

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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. 

            Assignee:
            Tobias Gruetzmacher
            Reporter:
            Steven Foster
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: