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.
note
Simultaneous usage of snapshot dependency and dependency trigger for a build Assume build A depends on build B by both snapshot and trigger dependency. Then after the build B finishes, build A will be added in the queue, only if build B is not a part of build chain containing A.
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 jar.
Maven repository URL
Specify URL to the Maven repository. Note, that this parameter is optional. If the URL is not specified, then:
For a Maven project the repository URL is determined from the POM and the server-side Maven Support
For a non-Maven project the repository URL is determined from the server-side Maven Support only