Copying and Moving Build Configuration
Last modified: 20 April 2023Copying Build Configuration
TeamCity allows administrator to create a copy of a build configuration. Such copy duplicates parameters and 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. A copy of a build configuration can be created in the same or in another project.
Copy Build Configuration Dialog
Option | Description |
|---|---|
Copy to project | Select a project to copy the build configuration to. By default the current project is selected. |
New configuration name | Name for the build configuration copy. Mandatory parameter. |
Copy users notification rules associated with this build configuration | If selected, all currently specified notification rules will be copied for a new configuration. |
Non-shared VCS Roots options | If you copy a build configuration to another project and there is at least one non-shared VCS root attached to the current build configuration, you will get a notification and will be prompted to select either of the following options. |
Use copies of these VCS roots in new build configuration | If selected, TeamCity automatically creates a copy of non-shared VCS root for a project the configuration is moved to. This new root will be also non-shared, available for the project the build configuration is moved into and will have an automatically generated name which looks like "Copy of <original VCS Root's name>" |
Share these VCS roots | With this option selected, TeamCity will automatically share any non-shared VCS root attached to the current configuration while copying. |
Moving Build Configuration
tip
This option is available since Calcutta 4.1 EAP (build 8725) Release Notes.
TeamCity allows moving build configurations between projects preserving their settings and associated data.
When a configuration is moved all its build history and dependencies will be preserved.
Build Configuration Dialog
Option | Description |
|---|---|
Move to project | Select a project to move current build configuration to. |
Non-shared VCS Roots options | If there is at least one non-shared VCS root attached to the current build configuration, you will get notification and will be prompted to select either of the following options. |
Use copies of these VCS roots in new build configuration | If selected, TeamCity automatically creates a copy of non-shared VCS root for a project the configuration is moved to. This new root will be also non-shared, available for the project the build configuration is moved into and will have an automatically generated name which looks like "Copy of <original VCS Root's name>" |
Share these VCS roots | With this option selected, TeamCity will automatically share any non-shared VCS root attached to the current configuration while moving. |
Thanks for your feedback!