You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Configuration Conditions are used as a way to queue or discard a build if certain conditions are met. When creating a condition, you provide a behavior, the build type it's applied to and a list of conditions. The following image shows the dialog when creating a configuration condition.

Behavior

This field defines the behavior of the build when the conditions are met. You can choose between Queue and Discard.

Queue

When any of the conditions are met, the build will be put on the queue rather than started immediately. This is handy for situations where you want to control when you want builds run. For example, you could configure it so no builds run during 9-5 work hours or perhaps during week days. You can also set it up so it queues a build until there's a new change set.

Discard

When any of the conditions are met, the build won't be run at all and will be marked as discarded. This is handy for situations where you don't want builds queuing up continuously. For example, you might create a condition that discards the build when there's no new change sets. You could setup a Queue behavior for that particular condition but the problem with queue is, any time a build is started it will be queued and subsequently run eventually. With discard the build is stopped and will never run again.

 

Applied to

The Applied to field stipulates which type of builds the conditions are applied. The three options are User, for when the build is manually started by a user, Trigger, when a build was triggered by a previously configured Triggers and Any, which applies the conditions to both User and Trigger builds.

 

Conditions

The conditions listed here are the same as the other conditions in Continua. You can use the query syntax in the fields and supply multiple conditions. A Configuration condition is defined as being both the Behavior and Applied to, plus the conditions listed here. You could also refer to these conditions as a Configuration condition's conditions. Regardless of the behavior of a Configuration condition, if any of the Configuration condition's conditions evaluate to true, then the specified behavior will result. Another way to interpret it would be: "If any of these conditions evaluate to true, my build will be Queued/Discarded".

  • No labels