-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
lockable-resources 1.11
https://issues.jenkins-ci.org/browse/JENKINS-34268 was closed implementing the possibility to lock a resources using a label in pipelines.
But there is no syntax for knowing what the actually locked resource name is when using a pipeline and locking on a label.
Specifically the proposed syntax from https://github.com/jenkinsci/lockable-resources-plugin/pull/36 : ", 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 want to lock a resource (host name) from the label and then ssh to that machine and execute some build steps. This works with the FreestyleJob functionality of "Reserved resources variable name".
Solution
It is now possible to access the locked resource via an configurable environment variable.
lock(label: 'some_resource', variable: 'MY_VAR') { echo env.MY_VAR }
- is related to
-
JENKINS-50176 Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks
-
- Resolved
-
- links to
[JENKINS-40997] Add way to get locked resource name in pipeline
Staffan Forsell
created issue -
| Assignee | New: Julian F. [ f_julian ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Description |
Original:
https://issues.jenkins-ci.org/browse/JENKINS-34268 was closed implementing the possibility to lock a resources using a label in pipelines. But there is no syntax for knowing what the actually locked resource name is when using a pipeline and locking on a label. Specifically the proposed syntax from https://github.com/jenkinsci/lockable-resources-plugin/pull/36 : ", 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 resource (host name) from the label and then ssh to that machine and execute some build steps. This works with the FreestyleJob functionality of "Reserved resources variable name". |
New:
https://issues.jenkins-ci.org/browse/JENKINS-34268 was closed implementing the possibility to lock a resources using a label in pipelines. But there is no syntax for knowing what the actually locked resource name is when using a pipeline and locking on a label. Specifically the proposed syntax from [https://github.com/jenkinsci/lockable-resources-plugin/pull/36] : ", 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 resource (host name) from the label and then ssh to that machine and execute some build steps. This works with the FreestyleJob functionality of "Reserved resources variable name". h4. Solution It is now possible to access the locked resource via an configurable environment variable. {code:java} lock(label: 'some_resource', variable: 'MY_VAR') { echo env.MY_VAR } {code} |
| Remote Link | New: This issue links to " PR #50 (Web Link)" [ 15835 ] |
| Remote Link | New: This issue links to "PR #49 (Web Link)" [ 20098 ] |
| Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Review [ 10005 ] | New: Resolved [ 5 ] |
| Link |
New:
This issue is related to |
| Description |
Original:
https://issues.jenkins-ci.org/browse/JENKINS-34268 was closed implementing the possibility to lock a resources using a label in pipelines. But there is no syntax for knowing what the actually locked resource name is when using a pipeline and locking on a label. Specifically the proposed syntax from [https://github.com/jenkinsci/lockable-resources-plugin/pull/36] : ", 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 resource (host name) from the label and then ssh to that machine and execute some build steps. This works with the FreestyleJob functionality of "Reserved resources variable name". h4. Solution It is now possible to access the locked resource via an configurable environment variable. {code:java} lock(label: 'some_resource', variable: 'MY_VAR') { echo env.MY_VAR } {code} |
New:
https://issues.jenkins-ci.org/browse/JENKINS-34268 was closed implementing the possibility to lock a resources using a label in pipelines. But there is no syntax for knowing what the actually locked resource name is when using a pipeline and locking on a label. Specifically the proposed syntax from [https://github.com/jenkinsci/lockable-resources-plugin/pull/36] : ", 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 want to lock a resource (host name) from the label and then ssh to that machine and execute some build steps. This works with the FreestyleJob functionality of "Reserved resources variable name". h4. Solution It is now possible to access the locked resource via an configurable environment variable. {code:java} lock(label: 'some_resource', variable: 'MY_VAR') { echo env.MY_VAR } {code} |