-
Improvement
-
Resolution: Unresolved
-
Major
-
None
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
- is duplicated by
-
JENKINS-44141 Define a resource pool
-
- Open
-
- is related to
-
JENKINS-34273 Extend quantity configuration to Pipeline lock step
-
- Resolved
-
- relates to
-
JENKINS-42209 Support for locking of multiple resource labels/groups
-
- Closed
-
We are also looking for something similar, we have a system running automation where we need to reserve resources dynamically some of them being clients and other being servers. Having the lock in a single step is highly important for us, however we don't always have the same number of servers as we have clients. We tried a workaround by creating a list of label or a chain of string ['CLIENT', 'CLIENT', 'CLIENT', 'SERVER'] hoping that this can help us circumvent the problem but that's not how the plugin seems to work.