jenkinsci / jenkinsci/lockable-resources-plugin
Multi-configuration project jobs start without acquiring a resource
Open
parallelism and races
resource conflicts or cleanup handled poorly
Triage
- Dominant language
- Java
- Stars
- 99
- Forks
- 205
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 8
Description
We are using a Groovy expression to acquire locks. This normally works fine, but in about 5-10% of the triggered jobs they will start without acquiring a resource.
The Groovy expression is:
```
if ( resourceLabels.contains("selenium_"+EDITION) && resourceName.startsWith("SELENIUM_") )
{
return true
}
return false
```
Our Jenkins installation is at version 2.138.2 and we are using version 2.3 of the lockable resources plugin.
Any hint how to solve this is welcome as we have to abort and fail the jobs, which did not receive a valid resource.
Contributor guide
Assessment
This issue has not been assessed yet.