Build Artifact

Artifacts are files produced by a build, for example, installers, WAR files, reports, log files, etc. After finishing a build, TeamCity searches for artifacts in the build's Build Checkout Directory according to the specified artifact patterns. Matching files are then uploaded to the server, where they become available for download. Artifacts stay on the server and are available for download until they are Clean-Up. Build Configurations can be configured to use artifacts of other builds (refer to Dependent Build for details).

You can specify artifacts of a build in the Configuring General Settings of the build configuration using comma-, or newline- separated values. The details on the format used to configure artifacts are described at the Configuring General Settings page.

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 Home Page. You can automate the 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 folder. Storage format is described in the TeamCity Data Directory section. The artifacts are stored on the server "as is" without additional compression, etc. TeamCity computer's administrator can delete artifacts directly form the disk. In this case, build's artifacts will no longer be available.

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 Build Script Interaction with TeamCity