Shared resource locks can be specified at configuration or stage level. At configuration level, the build will sit in a queue until the lock can be acquired and the lock will be released when the build finishes. At stage level, the build stage will sit in a queue before reserving an agent until a lock can be acquired and the lock will be released when the stage execution finishes.
| Anchor | ||||
|---|---|---|---|---|
|
Configurations can be setup to require and acquire locks on Server Shared Resources while evaluating configuration conditions before starting each build. The number and types of locks required are specified in the Conditions step of the Configuration Wizard.
...
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.
Stage Shared Resource Locks
Stages can be setup to require and acquire locks on Server Shared Resources before selecting an agent and Agent Shared Resources while selecting an agent. The number and types of locks required are specified on the Shared Resource Locks tab of the Stage Options dialog.
...
The fields depend on the type of shared resource selected as with Configuration Shared Resource Locks as described above.
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.
...