Build Artifact

Skip to end of metadata
Go to start of metadata
You are viewing documentation of TeamCity 7.x, which is not the most recently released version of TeamCity. Please refer to the listing to choose another version.
Search

Searching TeamCity 7.x Documentation

Table of Contents

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

Upon build finish, TeamCity searches for artifacts in the build's checkout directory according to the specified artifact patterns. 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 Artifacts column of the build entry on those TeamCity pages that list the builds, or you can find 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 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 artifacts are stored under <TeamCity data directory>/system/artifacts directory. Storage format is described in the TeamCity Data Directory#artifacts section. The artifacts are stored on the server "as is" without additional compression, etc.

All artifacts stay on the server and are available for download until they are cleaned up.

Build artifacts can also be uploaded to the server while the build is still running. To instruct TeamCity to upload the artifacts, 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 maven-build-info.xml file that contains Maven-specific data collected during the build. 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 .teamcity directory in the root of build's artifacts.
  • Hidden artifacts are not listed at 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.

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's 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)



See also:

Labels:

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