Artifact Dependencies

Depend on

Specify the build configuration for the current build configuration to depend on. A dependency can be configured on a previous build of the same build configuration.

Get artifacts from

Specify the type of build whose artifacts are to be taken: last successful build, last pinned build, last finished build, build from the same chain (this option is useful when you have a snapshot dependency and want to obtain artifacts from a build with the same sources), build with a specific build number or the last finished build with a specified tag.

Build number

This field appears if you have selected build with specific build number in the Get artifacts from list_.
Specify here the exact build number of the artifact.

Build tag

This field appears if you have selected last finished build with specified tag in the Get artifacts from list.
Specify here the tag of the build whose artifacts are to be used. When resolving the dependency, TeamCity will look for the last successful build with the given tag and use its artifacts.

Build branch filter

This field appears if the dependency has a branch specified in the VCS Root settings. Allows setting a branch filter to limit source builds only to those in the matching branches. If not specified, the default branch is used.

Artifacts Rules

Here you specify the artifacts of the source build to be downloaded and the location on the agent they will be downloaded to before the dependent build starts.

A newline-delimited set of rules. Each rule must have the following syntax:

[+:|-:]SourcePath[!ArchivePath][=>DestinationPath]

Each rule specifies the files to be downloaded from the "source" build. The SourcePath should be relative to the artifacts' directory of the "source" build. The path can either identify a specific file, directory, or use wildcards to match multiple files. Ant-like wildcards are supported.
Downloaded artifacts will keep the "source" directory structure starting with the first * or ?.
DestinationPath specifies the destination directory on the agent where downloaded artifacts are to be placed. If the path is relative (which is recommended), it will be resolved against the build checkout directory. If needed, the destination directories can be cleaned before downloading artifacts. If the destination path is empty, artifacts will be downloaded directly to the checkout root.

Basic examples:

• Use a/b/**=>lib to download all files from a/b directory of the source build to the lib directory. If there is a a/b/c/file.txt file in the source build artifacts, it will be downloaded into the file lib/c/file.txt.

• At the same time, artifact dependency **/*.txt=>lib will preserve the directories structure: the a/b/c/file.txt file from source build artifacts will be downloaded to lib/a/b/c/file.txt.

ArchivePath is used to extract downloaded compressed artifacts. zip, 7zip, jar, tar, and tar.gz are supported.
ArchivePath follows general rules for SourcePath: ant-like wildcards are allowed, the files matched inside the archive will be placed in the directory corresponding to the first wildcard match (relative to destination path)
For example: release.zip!*.dll command will extract all .dll files residing in the root of the release.zip artifact.

Archive processing examples:

• release-*.zip!*.dll=>dlls will extract *.dll from all archives matching the release-*.zip pattern to the dlls directory.

• a.zip!**=>destination will unpack the entire archive saving the path information.

• a.zip!a/b/c/**/*.dll=>dlls will extract all .dll files from a/b/c and its subdirectories into the dlls directory, without the a/b/c prefix.

+: and -: can be used to include or exclude specific files from the download or unpacking. As +: prefix can be omitted: rules are inclusive by default, and at least one inclusive rule is required. The order of rules is unimportant. For each artifact the most specific rule (the one with the longest prefix before the first wildcard symbol) is applied. When excluding a file, DestinationPath is ignored: the file won't be downloaded at all. Files can also be excluded from archive unpacking. The set of rules applied to the archive content is determined by the set of rules matched by the archive itself.

Exclusive patterns examples:

• **/*.txt=>texts
-:bad/exclude.txt Will download all *.txt files from all directories, excluding exclude.txt from the bad directory

• +:release-*.zip!**/*.dll=>dlls -:release-0.0.1.zip!Bad.dll Will download and unpack all *.dll files from release-*.zip files to the *.dll s' directory. The Bad.dll file from release-0.0.1.zip will be skipped

• **/*.*=>target
-:excl/**/*.*
+:excl/must_have.txt=>target Will download all artifacts to the target directory. Will not download anything from the excl directory, but the file called must_have.txt

The artifacts placed under the .teamcity directory are considered hidden. These artifacts are ignored by wildcards by default.
If you want to include files from the .teamcity directory for any purpose, be sure to add the artifact path starting with .teamcity explicitly.

Example of accessing hidden artifacts:

• .teamcity/properties/*.properties
• .teamcity/*.*

By default, downloading artifact dependencies to the agent work directory is allowed, the agent home directory is prohibited. To override the defaults, set custom rules to download artifacts by specifying the comma-separated paths in the buildAgent.properties: teamcity.artifactDependenciesResolution.blackList and teamcity.artifactDependenciesResolution.whiteList. Blacklisting a path forbids artifacts download to the directory unless it is whitelisted.

Clean destination paths before downloading artifacts

Check this option to delete the content of the destination directories before copying artifacts. It will be applied to all inclusive rules.