Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 8 Current »

You are viewing documentation of TeamCity 6.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.

Table of Contents

Dependency triggers allow to start the build every time the build it depends on finishes successfully. Please note, that you can also use dependencies (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 Settings.


Simultaneous usage of snapshot dependency and dependency trigger for a build

  The license could not be verified: License Certificate has expired!

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:



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 table below.


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 Settings
  • For a non-Maven project the repository URL is determined from the server-side Maven Settings only

For specifying version ranges use the following syntax, as proposed in the Maven documentation:




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

  The license could not be verified: License Certificate has expired!