Unable to render embedded object: File (TeamCity48.png) not found.

TeamCity 2018.x Documentation

Documentation for Previous Versions


You are viewing the documentation of TeamCity 2018.x, which is not the most recently released version of TeamCity.
View this page in the latest 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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Since TeamCity 10.0, it is possible to export settings of a project with its children to an archive to later import it to a different TeamCity server. Export includes settings (basically everything configured in the project administration area), but does not include builds or any other data visible in the user area. To export a project with all the related data, use server backup.

On this page:

Exporting Project Settings

To export the project settings, perform the following: 

  1. Go to the project settings, from the Actions menu in the top right of the project settings page select Export Project...:

  2. The Settings Export page is displayed allowing exporting the project and viewing all its dependencies. Click Export to download a zip archive containing project settings.

The user exporting the project settings must have the 'view build configuration settings' permission granted to the project developer role by default.  External dependencies are exported only if the user has the required permission there, otherwise a warning will be shown before export.

Export Scope

Currently only the settings export is supported.

External dependencies for build configurations are exported as well. A build configuration defined in one project can depend on other projects in a number of ways: it can

The report.log file included in the archive details reasons for exporting external entities.

Export Limitations

  • Builds, changes, and other project-related data cannot be exported.
  • External build configurations that are used in artifact dependencies only are not exported.







  • No labels