Thanks for fixing this. I observed that currently there is no way to configure the quantity of specific resource and we are forced to add lots of duplicated resources in order to overcome this. Still this does not scale and after 5-10 clones it becomes too hard to add additional. Due to this I raised JENKINS-42339 for adding a quantity inside the configure screen.

We are also looking for something like ssbarnea. 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.

Am I the only person who's ended up looking at this ticket to try and work out what the 'quantity' flag actually does? If I have a lockable resource called 'abc' and I say lock (resource: 'abc', quantity: 3), what does that actually do? I expected to somewhere set the maximum number of things available to lock within 'abc' and then the pipeline scripts could acquire 3 of them, but I don't see how to set the max. So it acquires 3, out of...?

tstibbs Did you figure out how to set the maximum? I'm facing the same lack of documentation as you.

rbjorklin, tstibbs: you need to copy the instance multiple times and group them by label. So you create

• resource1, label: my_resource
• resource2, label: my_resource
• resource3, label: my_resource
• resource4, label: my_resource
• resource5, label: my_resource

Now you have my_resource with a quantity of 5.