Configuring Dependency Triggers
Dependency triggers allow to start the build every time the build it depends on finishes successfully. Please note, that you can also use Dependent build (snapshot or artifacts) to trigger your builds automatically.
From Build Triggering page you can add the following dependency triggers:
Maven Snapshot Dependency Trigger
Maven snapshot dependency trigger adds a new build to the queue when any of the snapshot dependencies is updated in the remote repository. Dependency artifacts are resolved according to the POM and the server-side Maven Support.
Maven Artifact Dependency Trigger
Maven artifact dependency trigger adds build to the queue when specified Maven artifact changes. To add such trigger, specify the following parameters in the Add New Trigger dialog:
Parameter | Description |
|---|---|
Group Id | Specify identifier of a group the desired Maven artifact belongs to. |
Artifact Id | Specify the artifact's identifier. |
Version or Version range | Specify version or version range of the artifact. The version range syntax is described in the versionRanges below. |
Type | Define explicitly the type of the specified artifact. By default, the type is |
Maven repository URL | Specify URL to the Maven repository. Note, that this parameter is optional. If the URL is not specified, then:
|
For specifying version ranges use the following syntax, as proposed in the Maven documentation:
Range | Meaning | |
|---|---|---|
| x <= 1.0 | |
| "Soft" requirement on 1.0 (just a recommendation - helps select the correct version if it matches all ranges) | |
| Hard requirement on 1.0 | |
| 1.2 <= x <= 1.3 | |
| 1.0 <= x < 2.0 | |
| x >= 1.5 | |
| x <= 1.0 or x >= 1.2. Multiple sets are comma-separated | |
| This excludes 1.1, if it is known not to work in combination with this library |