3.1

Build Dependencies

In TeamCity, you can independently configure artifact dependencies and dependent build triggering. The former makes it possible to use artifacts of one build while building another one (for instance, to pass a library file created by one build to another). The latter provides a way to trigger a build when another build successfully finishes.

When creating new builds, it's possible to use the artifacts of:

• the last successful build,
• a successful build,
• the last finished build (including failed builds)
• a build with a particular number

You can use file patterns in the artifacts paths.

Keep your artifacts in order by specifying the destination directory where the artifacts will be downloaded when the build is started, and select whether or not you want to clean (delete all the existing files) the catalog before downloading artifacts.

It is now possible to view information on build artifacts that were used to create the build on the Dependencies page.

Artifacts

Artifacts are files and folders, such as installers, WAR files, log files, etc., produced by a build.

You can download artifacts from multiple places in TeamCity's UI: the Projects page, the Build Configuration page or the Artifacts tab of the Build Results page.

Publishing Build Artifacts while the Build is Still Running

Now you can notify TeamCity as soon as the build artifacts are created so they can be uploaded and available even before the build is finished. It increases your builds responsiveness and you don't need to wait until your builds are finished.

Build Tags

TeamCity introduces build tagging — a useful means for organizing the builds and quick filtering builds marked with a particular tag in the builds history. You can apply one or several tags to a single build.

Additionally you can now search for builds marked with particular tags.

History

The builds, which TeamCity produces, are kept in the history.

To limit your database of builds and, thus, manage the hardware load more effectively, you can specify the clean-up policy using the administration interface.

If you don't want builds with all related information, artifacts, etc. to be removed from the database, pin the desired build, and you will always be able to access its artifacts. This can be especially useful if you want to keep the artifacts of some error-free build intended for release or other purposes.

VCS Revisions

TeamCity now provides information on:

• files revisions
  

  

  
  
• project repository revisions (the number of repository revision which was used to create a build)
  

  

  
  

Search for Builds Using Keywords

Find builds by their number, tag, or build configuration name. You can use several keywords to get more precise results.

Search for builds run on a Build Agent and filter history by Agent name

In addition to searching by build number, project or a build configuration name, you can now search by the Build Agent the build was run on, and it's also possible to search for the builds created on a particular Build Agent on the build configuration History page.