You are viewing the documentation of TeamCity 10.x and 2017.x, which is not the most recently released version of TeamCity.
View this page in TeamCity 2018.x documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.

Skip to end of metadata
Go to start of metadata

A build configuration can be made dependent on the artifacts or sources of builds of some other build configurations.

For snapshot dependencies, TeamCity will run all dependent builds on the sources taken at the moment the build they depend on starts.

For artifact dependencies, before a build is started, all artifacts this build depends on will be downloaded and placed in their configured target locations and then will be used by the build.


The dependencies of the build can later be viewed on the build results page - the Dependencies tab. This tab also displays indirect dependencies, e.g. if a build A depends on a build B which depends on builds C and D, then these builds C and D are indirect dependencies for build A.

See also:

Concepts: Dependent Build
Administrator's Guide: Accessing artifacts via HTTP | Snapshot Dependencies | Artifact Dependencies
External Resources: http://ant.apache.org/ivy/ (additional information on Ivy)