[JIRA] (JENKINS-34268) Lock multiple resources using the Pipeline lock step

[stalle+jenkins...@gmail.com (JIRA)]

Title: Message Title

Staffan Forsell commented on JENKINS-34268   Re: Lock multiple resources using the Pipeline lock step Antonio Muñiz Hi! Nice to see this merged. Looking at the merged content, I can't seem to find any pipeline syntax for actually knowing what resource was locked. Specifically the proposed syntax from PR36 above: ", variable: 'MY_VAR'" is missing. Our use case is that we wan't to specify a label containing node names for legacy builders that can't run the slave.jar (java7) anymore. We wan't to lock a resources (host name) from he label and then ssh to that machine any execute some build steps. This works with the FreestyleJob functionality of #Reserved resources variable name". Any thought of adding this to pipeline? Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.