www.jetbrains.com
Open in
urlscan Pro
108.157.4.36
Public Scan
URL:
https://www.jetbrains.com/help/teamcity/project-export.html
Submission: On May 30 via api from US — Scanned from DE
Submission: On May 30 via api from US — Scanned from DE
Form analysis
0 forms found in the DOMText Content
TeamCity On-Premises 2022.04 Get TeamCity On-Premises * TeamCity On-Premises Documentation Home * Getting Started with TeamCity * Terms and Concepts * Installation and Upgrade * System Administration * Managing Projects * Creating and Editing Projects * Project Export * Projects Import * Configuring VCS Settings * Configuring Connections * Storing Project Settings in Version Control * Ordering Projects and Build Configurations * Configuring Cross-Server Projects Pop-up Menu * Archiving Projects * Customizing Statistics Charts * Configuring Artifacts Storage * Managing Build Configurations * Configuring Test Reports and Code Coverage * Running Builds and Viewing Results * Integrating TeamCity with Other Tools * Extending TeamCity and Using REST API for Integration * Reference * Licensing and Release Cycle * Troubleshooting * CI Tutorials * Other resources 1. Managing Projects 2. Project Export PROJECT EXPORT Edit page Last modified: 25 May 2022 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. EXPORTING PROJECT SETTINGS To export the project settings, perform the following: 1. Go to Project Settings, from the Actions menu in the upper right corner 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 The export scope of a project contains only this project's settings, including private SSH keys uploaded by the project administrator. 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: * be associated with a template defined in the parent projects; * use VCS roots or an SSH key defined higher in the project hierarchy; * use some external build configuration as a snapshot dependency. 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. Thanks for your feedback! Was this page helpful? YesNo * Project Export * Exporting Project Settings * Export Scope * Export Limitations Creating and Editing ProjectsProjects Import Contact us Copyright © 2000–2022 JetBrains s.r.o.