You are viewing the documentation of TeamCity 10.x and 2017.x, which is not the most recently released version of TeamCity.
View this page in TeamCity 2018.x documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.

Skip to end of metadata
Go to start of metadata

TeamCity contains an integrated lightweight builds artifact repository. The artifacts are stored wither on the server-accessible file system or (since TeamCity 2017.1) on an external storage. 

Build artifacts are files produced by a build and stored on the TeamCity server. Typically these include distribution packages, WAR files, reports, log files, etc. When creating a build configuration, you specify paths to the artifacts of your build at the General Settings page.

Upon the build finish, TeamCity searches for artifacts in the build checkout directory according to the specified artifact path or path patterns. The matching files are then uploaded ("published") to the TeamCity server, where they become available for download through the web UI or can be used in other builds using artifact dependencies.

To download artifacts of a build, use the Artifacts column of the build entry on the TeamCity pages that list the builds, or locate them at the Artifacts tab of the build results page. You can automate artifacts downloading as described in the Patterns For Accessing Build Artifacts section.

TeamCity stores artifacts on the disk in a directory structure that can be accessed directly (for example, by configuring the Operating System to share the directory over the network). The storage format is described in the TeamCity Data Directory#artifacts section. The artifacts are stored on the server "as is" without additional compression, etc. By default, the artifacts are stored under the <TeamCity data directory>/system/artifacts directory which can be changed.

Build artifacts can also be uploaded to the server while the build is still running. To instruct TeamCity to upload the artifacts, the build script should be modified to send service messages.

Hidden Artifacts

In addition to user-defined artifacts, TeamCity also generates and publishes some artifacts for internal purposes. These are called hidden artifacts.
For example, for Maven builds, TeamCity creates the maven-build-info.xml file that contains Maven-specific data collected during the build. The content of the file is then used to visualize the Maven data on the Maven Build Info tab in the build results.

  • Hidden artifacts are placed under the .teamcity directory in the root of the build artifacts.
  • Hidden artifacts are not listed on the Artifacts tab of the build results by default. However, below the list of the artifacts there's a link that allows you to view hidden artifacts if any. When hidden artifacts are displayed, clicking the Download all link will result in downloading all artifacts including hidden ones.
  • Artifacts dependencies do not download hidden artifacts unless they explicitly have ".teamcity" in the pattern.
  • Hidden artifacts are not deleted by artifacts clean-up unless ".teamcity" is explicitly specified in the pattern.

You can configure publishing for some of builds artifacts under .teamcity directory to make them hidden.

Some of the hidden artifacts are:

  • maven-build-info.xml.gz - Maven build data. Used to display data on Maven Build Info build's tab.
  • properties directory - holds properties calculated for the build on the agent. There are properties actual before the build and after the build. These are displayed on the build Properties tab.
  • .NETCoverage - raw .Net coverage data (e.g. used to open dotCover data in VS addin)
  • coverage_idea - raw IntelliJ IDEA coverage data (e.g. used to open coverage in IDEA)

Artifacts Cache on Agent

All artifacts published by a build are stored in the agent's artifacts cache in the <Build Agent home>\system\.artifacts_cache directory, which helps speed up artifact dependencies in some cases. However, depending on the size of artifacts, clean-up and other settings, artifacts caching may cause low disk space on the agent. You can configure storing published artifacts in the agent cache.

See also: