jenkinsci / jenkinsci/lockable-resources-plugin
[JENKINS-42339] each lockable resource should have a quantity field which defaults to 1
- Dominant language
- Java
- Stars
- 99
- Forks
- 205
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 8
Description
It seems the current implementation for the quantity does require jenkins administrators to define different duplicated/identical resources because they cannot define a quantity.
This is a serious scalability resources which make harder to implement resources locking for resources that are supposed to be in bigger numbers like: total RAM available or total number of VCPUs. For example in our testing cloud we do have 300 GB RAM and 300 VCPU limit.
Now is effectively impossible to use the locking plugin for this because we would have to create 600 resource entries in the config, probably the browser will crash before we would be able to add all of these ![]()
---
Originally reported by
ssbarnea, imported from: each lockable resource should have a quantity field which defaults to 1
Raw content of original issue
It seems the current implementation for the quantity does require jenkins administrators to define different duplicated/identical resources because they cannot define a quantity.
This is a serious scalability resources which make harder to implement resources locking for resources that are supposed to be in bigger numbers like: total RAM available or total number of VCPUs. For example in our testing cloud we do have 300 GB RAM and 300 VCPU limit.
Now is effectively impossible to use the locking plugin for this because we would have to create 600 resource entries in the config, probably the browser will crash before we would be able to add all of these
Contributor guide
Research direction
Start by locating the lockable resource model, its Jenkins configuration entry points, and tests covering resource allocation. Trace how a configured resource is represented and consumed by locking, then define done as supporting a quantity that defaults to 1 without requiring duplicated entries, including coverage for larger quantities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100