Configuring Dependencies

Skip to end of metadata
Go to start of metadata
You are viewing documentation of TeamCity 6.5.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.

Searching TeamCity 6.5.x Documentation

Table of Contents

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 the build is started to run, all artifacts the builds depends on will be downloaded and placed in their configured target locations and then can be used by the build.

The dependencies of the build can later be viewed on the build results page - Dependencies tab. This tab displays also 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 the build A.

See also:

Concepts: Dependent Build
Administrator's Guide: Accessing artifacts via HTTP | Snapshot Dependencies | Artifact Dependencies
External Resources: (additional information on Ivy)


dependency dependency Delete
artifact artifact Delete
ivy ivy Delete
ant ant Delete
configure configure Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.