...
| Info |
|---|
Note that Shared Resource Lock conditions are available from version 1.8 |
Creating and Editing Configuration Conditions
Configuration conditions can be created, edited or deleted within the Conditions step of the Configuration Wizard.
New/Edit Condition
Behaviour
This field defines the behaviour of the build when the conditions are met. You can choose between Queue and Discard.
Queue
A Queue condition controls when a build should begin executing.
...
You could also configure a queue condition to require one of three available licences for a particular application. To set this up, you would first create a Server Shared Resource called "License.XApp", for example. Next, create a queue condition of type "Shared resource lock" and add the identifier: "License.XApp". Select "Read" lock and enter 1 for the number of locks required (as seen in the screenshot below). With this condition, once three builds are running and have acquired a lock on this resource, subsequent build will sit on the queue until one build finishes and releases a shared resource lock.
Discard
A discard condition will stop a build before it is executed if any or all of its expressions evaluate to true, depending on the Expression Logic (see below). Note that discard conditions are always expressions - you cannot have discard conditions based on shared resource locks. The difference between discarding and queueing queuing a build is that a discarded build will never run again while a queued build can run at a later time. Discarding builds is useful when certain types of builds should never get built.
...
Queue conditions can either be of type "Expression" or "Shared resource lock". Selecting "Expression" allow you to enter expressions which can be evaluated as true or false. Selecting "Shared resource lock" will alow allow you to enter a list of shared resource identifiers along with lock type and number required.
...