...
Add a new condition, select the "Queue" behaviour and then select the "Shared resource lock" condition type. Note that shared resource lock can only be added to queue conditions, builds can not be discarded based on shared resource locks.
Choose an existing shared resource Identifier. Only server shared resources can be selected for a configuration, locks on agent shared resources are configured on a stage - see next section on Stage Shared Resource Locks. The additional fields depend on the type of shared resource.
No further details are required for a lock on a Single shared resource as shown below:
With Quota shared resources, you can specify the type of Lock: Read or Write. If you choose to acquire a Read lock then you can enter the Number of locks required from the allocated quota.
Likewise with Infinite shared resources.
Quota list shared resources have several more options. You can choose an Operation. The choices are as follows:
...
You can also select the type of Lock: Read or Write. If you choose to acquire a Read lock then you can enter the Number of locks required from the allocated quota of a label.
You can add or remove rows using + and - buttons at the end of each row. If multiple shared resource locks are defined, the build will sit in the queue until all locks are acquired.
...
When a stage is queued, Continua CI will first attempt to acquire any server shared resources. Once these are acquired, the system will attempt to find an available and compatible agent with the required quota of any agent shared resources. If more than one suitable agent has any available allocate of the resource, then the one with the highest number will be selected to execute the stage.