Artifacts Dependencies

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

 Artifacts Dependencies

Administration > <project> > Artifact Dependencies

Artifact Dependencies

 If build configuration contains artifact dependencies, the following information is presented for each dependency:

Option Description
Artifacts source
Dependency in the format:

<Project name>::<Build configuration name> <Where the artifact is taken from>
                        

Artifacts path
Path to the artifact dependency on the server.
Destination path
Target location of the dependency on the build agent.
Edit Click this link to modify the selected dependency.
Delete
Click this link to remove the selected dependency.

Add / Edit Dependency 

Option Description
Add new dependency
Click this link to specify the artifacts dependency.
Depend on
Specify build configuration which the current build configuration should depend on.
Get artifacts from Specify the type of build. from which the artifacts should be taken. The following options are available:
  • Last successful build
  • Last pinned build
  • Last finished build
  • Build number 
    Note

    When selecting build type, take into account the settings of your clean-up policy. Builds are cleaned off on the regular basis, and the build configuration might become dependent on a non-existent build. If the artifacts are taken from a build with the specified number, or from a pinned build, such builds are not deleted.

Build number Use this field to specify the exact build number of the artifact. This field is enabled, if Build number option is selected in the Get artifacts from field.
Artifacts path Specify an artifact path of the "source" build. Path should be relative to artifacts directory of the "source" build. Path can be either exact name of a file, directory (all children of the directory will be copied), or it can be defined as regular expression.
(since 2.1) wildcards (*, ?) should be used in artifact path instead of regular expressions
More artifacts Click this link to open an additional text field, where you can specify the path to another artifacts.
Destination path
Specify destination path on the agent where downloaded artifacts should be placed. If the path is relative, it will be resolved against build working directory. If needed, destination path can be cleaned before downloading artifacts.
Clean history before downloading artifacts Check this option to delete the content of the destination directory before copying artifacts.
Save Preserve changes and close the page. 

See also

Configuring Artifact Dependencies

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.