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

To copy, move or delete a build configuration, use the Actions menu on the right of the build configuration settings pages.

Copy and Move Build Configuration

Build configurations can be copied and moved to another project by project administrators:

  • A copy duplicates all the settings of the original build configuration, but no data related to builds is preserved. The copy is created with empty build history and no statistics. You can copy a build configuration into the same or another project.
  • When moving a build configuration between projects, TeamCity preserves its settings and associated data, as well as its build history and dependencies.

On copying, TeamCity automatically assigns a new ID to the copy. It is also possible to change the ID manually.
Selecting the Copy associated user, agent and other settings option makes sure that all the settings like notification rules or agent's compatibility are exactly the same for the copied and original build configurations for all the users and agents affected.

If the build configuration uses VCS Roots or is associated with a template which is not accessible in the target project (does not belong to the target project or one of its parent projects), the copies of these VCS roots and the template will be created in the target project. (see also related issue TW-28550)


When running TeamCity in the Professional mode with the maximum allowed number of build configurations (100 build configurations since TeamCity 2017.2 (20 in earlier versions) unless you purchased additional Build Agent licenses), the Copy option will not be displayed for build configurations.

Delete Build Configuration

When you delete a build configuration, TeamCity will remove its .xml configuration file. After the deletion, there is a configurable timeout (24 hours by default) before the builds of the deleted configuration are removed during the build history clean-up.


If you attempt to delete a build configuration which has dependent build configurations, TeamCity will warn you about it. If you proceed with deletion, the dependencies will no longer function.