Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-42339

each lockable resource should have a quantity field which defaults to 1


      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

            Unassigned Unassigned
            ssbarnea Sorin Sbarnea
            20 Vote for this issue
            13 Start watching this issue