[JIRA] (JENKINS-56408) Lockable resources plugin doesn't assign resource if an env variable is used as label

[tobias-jenk...@23.gs (JIRA)]

Title: Message Title

Tobias Gruetzmacher commented on JENKINS-56408   Re: Lockable resources plugin doesn't assign resource if an env variable is used as label Can you change the lockable resource plugin so that the name of the resource is determined when the plugin is executed and not at the beginning of the pipeline? No, I cannot. What you are experiencing here are the normal scoping rules of declarative pipeline: The options blocks are "run" when the declarative pipeline is build, while the steps block is run when the pipeline is executed. If you want a different order, you need to fall back to scripted pipeline. (Or report a bug against the declarative pipeline plugin, but I suspect this is considered part of the design) Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197999.1551776838000.1389.1570236660461%40Atlassian.JIRA.