-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
-
lockable-resources 1.11
My CI server has multiple executors and multiple android devices attached to it. Each executor can perform either android or linux build. If android build is being performed, a test must be also performed on the device. To ensure unique access to specific android device, I use lockable resources plugin to "lock" the device.
However, in order to check if device1 is in use and then use device2, I am currently relying on custom locking logic (manually keeping lock files). It would be ideal if lockable resources plugin would have an option to enter the lock block if any of the listed resources can be acquired (and provide which resource was required).
For example:
lock_any( [ 'device1', 'device2', 'device3' ] ) { acquired_device -> // run tests on ${acquired_device} }
[JENKINS-44515] Implement lock_any option for pipelines
Nenad Miksa
created issue -
Tobias Gruetzmacher
made changes -
| Released As | New: lockable-resources 1.11 | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |