In TeamCity one build configuration can depend on one or more configurations. Two types of dependencies can be specified:
Artifact dependency is just a way to get artifacts produces by one build in another. Without corresponding Snapshot dependency they are mainly used when the build configurations are not related in terms of sources. For example one build provides a reusable component for others.
Snapshot Dependency is a powerful concept that allows to express dependencies between the build configurations on the source level in TeamCity.
A snapshot dependency from build configuration A to build configuration B enforces that each build of A has a "suitable" build of B so that both builds use the same sources snapshot (used sources revisions correspond to the same moment).
Snapshot dependency alters the builds behavior in the following way:
Let's consider an example to illustrate how snapshot dependencies work.
Let's assume that we have two build configurations, A and B, and configuration A has snapshot dependency on configuration B.
The above example shows the core basics of the snapshot dependencies - straight forward process without any additional options. For snapshot dependency options refer to the Snapshot Dependencies page.
Depending on the dependencies topology builds can run sequentially or in parallel.
Two or more builds connected by snapshot dependencies form the Build Chain.
See also related "Trigger on changes in snapshot dependencies" setting of a VCS trigger and "Show changes from snapshot dependencies" check box on "Version Control Settings" configuration section.
Artifact Dependencies provide you with a convenient means to use output (artifacts) of one build in another build. When an artifact dependency is configured, the necessary artifacts are downloaded to the agent before the build starts. You can then review what artifacts were used in a build or what build used artifacts of the current build on a Dependencies tab of build results.
To create and configure an artifact dependency use the Dependencies page. If for some reason you need to store artifact dependency information together with your codebase and not in TeamCity, you can configure Ivy Ant tasks to get the artifacts in your build script.
Skip to end of metadata Go to start of metadata