ARTIFACT_PATH is a path to artifact in TeamCity server. This path may contain a {build.number} pattern , this pattern will be replaced with build number of the build whose artifact is retrieved.

Obtaining Artifacts from an Archive

TeamCity allows to obtain a file from any zip/jar archive from the build artifacts directory, using one of the following URL patterns:

Pattern 1

where:

BUILD_TYPE_ID is a build configuration ID

lastFinished | lastSuccessful | lastPinned is an identifier for the build instance

Pattern 2

where

BUILD_TYPE_ID is a build configuration ID

BUILD_NUMBER is a build number

Obtaining Artifacts from a Build Script

It is often required to download artifacts of some build configuration by tools like wget or another downloader which does not support HTML login page. TeamCity asks for authentication if you accessing artifacts repository.

To authenticate correctly from a build script, you have to change URLs (add /httpAuth/ prefix to the URL):

Basic authentication is required for accessing artifacts by this URLs with /httpAuth/ prefix. You can use existing TeamCity username and password in basic authentication settings.

To enable downloading an artifact with guest user login, you can use either of the following methods:

Use old URLs without /httpAuth/ prefix, but with added guest=1 parameter. For example:

Add the /guestAuth prefix to the URLs, instead of using guest=1 parameter. For example:

In this case you will not be asked for authentication.
The list of the artifacts can be found in /repository/download/BUILD_TYPE_ID/.lastFinished/teamcity-ivy.xml.

Links to the Artifacts Containing the TeamCity Build Number

You can use {build.number} as a shortcut to current build number in the artifact file name.
For example:

Obtaining all artifacts in a single archive

TeamCity allows to download all artifacts packed in a zip archive using any of the following links:

where {build.number} and {build.type} denote the build id and build configuration id respectively.