Build Artifact

Artifacts are files produced by a build. After finishing a build, TeamCity searches for artifacts in the build's checkout directory according to the specified artifact patters. 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 the artifacts for the build are cleaned up. Examples of artifacts are installers, WAR files, reports, log files, etc.

Artifacts of a build are specified on the general settings page using comma-, or newline- separated values of the format:

file_name|directory_name|Ant-like wildcard [ => target_directory ]

The format contains:

• file_name — to publish the file. The file will be published by its name.
• directory_name — to publish all the files and subdirectories within the directory specified. The files will be published preserving the directories structure under the directory specified (the directory itself will not be included).
• wildcard — to publish files matching Ant-like pattern ("*" and "**" wildcards are only supported). The files will be published preserving the structure of the directories matched by the wildcards (directories matched by "static" text will not be created). That is, TeamCity will create directories starting from the first occurrence of the wildcard in the pattern.
• target_directory — the directory in the resulting build's artifacts that will contain the files determined by the left part of the pattern.

The names are relative to the build checkout directory.

An optional part starting with => symbols and followed by the target directory name can be used to publish the files into the specified target directory. If target directory is omitted the files are published in the root of the build artifacts. You can use "." (dot) as reference to the build checkout directory.

Examples:

• install.zip — publish file named install.zip in the build artifacts
• dist — publish the content of the dist directory
• target/*.jar — publish all jar files in the target directory
• target/**/*.txt => docs — publish all the txt files found in the target directory and its subdirectories. The files will be available in the build artifacts under the docs directory.
• reports => reports, distrib/idea.zip — publish reports directory as reports and files matching idea*.zip from the distrib directory into the artifacts root.

  TeamCity stores artifacts on disk in a directory structure that can be accessed directly (e.g. 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. Build artifacts are not archived in TeamCity and stay as they are (uncompressed).

  You can download artifacts of a build via the web UI from the Artifacts column of the Projects page, from the Overview tab of the Build Configuration Home Page or from the Artifacts tab of the Build Results page.
  Artifacts downloading can be automated as described in the section Patterns For Accessing Build Artifacts.

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

Artifacts are stored on the disk on the server, under TeamCity Data Directory/artifacts/<project name>/<build configuration name>/<internal_build_id> directory. The artifacts can be copied directly form the directory on the server (if OS is configured to provide access for it). TeamCity computer's administrator can delete artifacts directly form the disk. In this case, build's artifacts will no longer be available.

See also:

• Concepts: Dependent Build
• Administrator's Reference: Configuring Artifact Dependencies
• UI Reference: Artifact Dependencies | Projects