Requirement Conditions
This page explains conditions used in agent requirements or build step execution requirements.
Condition | Description and Example |
---|---|
exists | Returns For example:
|
does not exist | Returns For example:
|
equals | Returns You can leave the Value field empty to check whether the specified property exists but is empty. For example:
|
does not equal | Returns You can leave the Value field empty to check whether the specified property exists and is not empty (has a value). For example:
|
is not more than | Return For example:
|
is more than | |
is less than | |
is not less than | |
version is more than | Compare software versions with the given value. Supports multiple value formats, including dot ( For example:
|
version is not more than | |
version is less than | |
version is not less than | |
contains | Returns For example:
|
does not contain | Returns For example:
|
starts with | Returns For example:
|
ends with | |
matches | Returns For example, use |
does not match |
When multiple requirements are defined, they are implicitly joined by boolean AND. For example, the following set of conditions requires that both the env.JDK_17_0
parameter AND the env.JDK_21_0
parameter exist:
requirements {
exists("env.JDK_17_0")
exists("env.JDK_21_0")
}
There is no mechanism available for joining requirements with boolean OR.
Thanks for your feedback!