Creating and Editing Projects

Creating project pointing to repository URL

1. On the Create project page, select to create a project from a repository URL.

2. Specify the project settings:

3. Click Proceed. TeamCity will configure the rest of settings for you.

• it will determine the type of the VCS repository, autoconfigure VCS repository settings, and suggest the project and build configuration names.
  For a Git repository, TeamCity will autodetect the default branch, but you have an option to change it and to add other branches to monitor by entering their specification.

• the project, build configuration and VCS root will be created automatically.

• TeamCity will add a VCS build trigger.

• TeamCity will attempt to autodetect build steps: Ant, NAnt, Gradle, Maven, MSBuild, Visual Studio solution files, PowerShell, Xcode project files, Rake, and IntelliJ IDEA projects.

4. On the Auto-detected Build Steps page select the detected step(s) to use in your build configuration. Click Use selected. If no steps found, you will have to configure build steps manually.

5. Your project and a build configuration are configured. Click the Run button to start the build.
Depending on the build configuration settings, TeamCity can suggest some additional configuration options. Review Suggestions at the end of the settings list and configure required ones.

Creating project pointing to GitHub.com repository

1. On the Create project page, select to create a project from GitHub.com.

2. Select a repository. TeamCity will verify the repository connection. If the connection is verified, the new page opens.

3. TeamCity will display the project and build configuration name. If required, modify the names and click Proceed. TeamCity will autodetect the default Git branch, but you have an option to change it and to add other branches to monitor by entering their specification.

4. TeamCity will add a VCS build trigger and attempt to autodetect build steps: Ant, NAnt, Gradle, Maven, MSBuild, Visual Studio solution files, PowerShell, Xcode project files, Rake, and IntelliJ IDEA projects.
   On the Auto-detected Build Steps page, select the detected step(s) to use in your build configuration. Click Use selected.
   If no steps found, you will have to configure build steps manually.

5. Your project and a build configuration are configured. Click Run to start the build. Depending on the build configuration settings, TeamCity can suggest some additional configuration options. Review Suggestions at the end of the settings list and configure required ones.

Creating project pointing to Bitbucket Cloud

1. On the Create project page, select to create a project from Bitbucket Cloud.

2. Select a repository. TeamCity will verify the repository connection. If the connection is verified, the new page opens.

3. TeamCity will display the project and build configuration name. If required, modify the names and click Proceed. For a Git repository, TeamCity will autodetect the default branch, but you have an option to change it and to add other branches to monitor by entering their specification.

4. TeamCity will add a VCS build trigger and attempt to autodetect build steps: Ant, NAnt, Gradle, Maven, MSBuild, Visual Studio solution files, PowerShell, Xcode project files, Rake, and IntelliJ IDEA projects.
   On the Auto-detected Build Steps page, select the detected step(s) to use in your build configuration. Click Use selected.
   If no steps found, you will have to configure build steps manually.

5. Your project and a build configuration are configured. Click Run to start the build. Depending on the build configuration settings, TeamCity can suggest some additional configuration options. Review Suggestions at the end of the settings list and configure required ones.

Creating project pointing to GitLab.com

1. On the Create project page, select to create a project from GitLab.com.

2. Select a repository. TeamCity will verify the repository connection. If the connection is verified, the new page opens.

3. TeamCity will display the project and build configuration name. If required, modify the names and click Proceed. TeamCity will autodetect the default Git branch, but you have an option to change it and to add other branches to monitor by entering their specification.

4. TeamCity will add a VCS build trigger and attempt to autodetect build steps: Ant, NAnt, Gradle, Maven, MSBuild, Visual Studio solution files, PowerShell, Xcode project files, Rake, and IntelliJ IDEA projects.
   On the Auto-detected Build Steps page, select the detected step(s) to use in your build configuration. Click Use selected.
   If no steps found, you will have to configure build steps manually.

5. Your project and a build configuration are configured. Click Run to start the build. Depending on the build configuration settings, TeamCity can suggest some additional configuration options. Review Suggestions at the end of the settings list and configure required ones.

Creating project pointing to Azure DevOps Services

1. On the Create project page, select to create a project from Azure DevOps. The recommended approach for Git repositories is to use the connection based on OAuth 2.0 protocol. If you need to connect to a TFVC repository, use the obsolete PAT-based connection.

2. Select a repository. TeamCity will verify the repository connection. If the connection is verified, the new page opens.

3. TeamCity will display the project and build configuration name. If required, modify the names and click Proceed. For a Git repository, TeamCity will autodetect the default branch, but you have an option to change it and to add other branches to monitor by entering their specification.

4. TeamCity will add a VCS build trigger and attempt to autodetect build steps.
   On the Auto-detected Build Steps page select the detected step(s) to use in your build configuration. Click Use selected.
   If no steps found, you will have to configure build steps manually.

5. Your project and a build configuration are configured. Click Run to start the build. Depending on the build configuration settings, TeamCity can suggest some additional configuration options. Review Suggestions at the end of the settings list and configure required ones.

Creating project pointing to JetBrains Space

tip

If you are looking for how to integrate your JetBrains Space instance with TeamCity, check out this full integration guide!

Before creating a project from a JetBrains Space, you need to configure a dedicated connection to your Space instance.

1. On the Create project page, select to create a project from JetBrains Space. The first time, you will be prompted to sign in to Space and grant TeamCity access to view your user profile and projects. To be able to do this, TeamCity will create a service token for authenticating in your Space instance.

2. Select a repository. TeamCity will verify the repository connection. If the connection is verified, the new page opens.

3. TeamCity will display the project and build configuration names. If required, modify them and click Proceed. For a Git repository, TeamCity will autodetect the default branch, but you have an option to change it and to add other branches to monitor by entering their specification.

4. TeamCity will add a VCS build trigger and attempt to autodetect build steps.
   On the Auto-detected Build Steps page select the detected step(s) to use in your build configuration. Click Use selected.
   If no steps found, you will have to configure build steps manually.

5. Your project and a build configuration are configured. Click Run to start the build. Depending on the build configuration settings, TeamCity can suggest some additional configuration options. Review Suggestions at the end of the settings list and configure required ones.

Creating project manually

1. Click the Create project button and select Manually.

2. On the Create New Project page, specify the project settings:

3. Click Create. An empty project is created.

tip

To configure an existing project, select the desired project in the list, and click the Edit Project Settings link on the right.

4. Create build configurations (select build settings, configure VCS settings, and choose build runners) for the project.

5. Assign build configurations to specific build agents.

Copying Project

Use the corresponding item from the Actions menu in the upper right corner of the Project Settings page or the More button next to the project on the parent Project Settings page.

Projects can be copied and moved to another project by project administrators.

A copy duplicates all the settings, subprojects, build configurations, and templates of the original project, but no data related to builds is preserved. The copy is created with the empty build history and no statistics.

You can copy a project into the same or another parent.

On copying, TeamCity automatically assigns a new name and ID to the copy. It is also possible to change the name and ID manually.
Selecting the Copy project-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 projects for all the users and agents affected.

You can also opt to copy build configurations build numbers.

note

When running TeamCity in the Professional mode, the Copy option will not be displayed for a project if the number of build configurations on the server after copying will exceed the limit (100 build configurations, unless you purchased additional build agent licenses).

Moving Project

warning

Before moving the project, consider the following:

• TeamCity assigns user roles on a per-project basis, which means that moving a project may result in changing the scope of user permissions in the new project (new permissions may be added or the existing permissions can be dropped)

• Connection to Git VCS Roots containing SSH keys may get unavailable after a project move.

To move a project, use the corresponding item from the Actions menu in the upper right corner of the Project Settings page or the More button next to the project on the parent Project Settings page.

When moving a project, TeamCity preserves all its settings, subprojects, build configurations/templates, and associated data, as well as the build history.

Archiving Project

Use the corresponding item from the Actions menu in the upper right corner of the Project Settings page or the More button next to the project on the parent Project Settings page. Refer to the dedicated page.

Bulk Editing IDs

warning

Care must be taken when performing this action. Modifying the ID will change all the URLs related to the project. It is highly recommended to update the ID in any of the URLs bookmarked or hard-coded in the scripts. The corresponding configuration and artifacts directory names on the disk will change too and it can take time.

1. Use the corresponding item from the Actions menu in the upper right corner of the Project Settings page or the More button next to the project on the parent Project Settings page.

2. The current project and build configuration IDs are displayed. You can modify or reset the IDs for all subproject, VCS roots, build configurations and templates. Click Regenerate to get new Ids automatically or edit them manually.

3. Click Submit.

Pausing / Activating Triggers

You can pause triggers for all or selected build configurations of a project. Use the corresponding item from the Actions menu in the upper right corner of the Project Settings page or the More button next to the project on the parent Project Settings page.

Exporting Project

You can export configuration files of a project with its children to move it to a different TeamCity server. Use the corresponding item from the Actions menu in the upper right corner of the Project Settings page or the More button next to the project on the parent Project Settings page.

Deleting Project

Use the corresponding item from the Actions menu in the upper right corner of the Project Settings page or the More button next to the project on the parent Project Settings page.

When you delete a project, TeamCity will remove its .xml configuration files. After the deletion, the project is moved to the <TeamCity Data Directory>/config/_trash/.ProjectID.projectN directory. There is a configurable timeout (5 days by default) before all project-related data stored in the database (build history, artifacts, and so on) of the deleted project is completely removed during the next build history clean-up.

tip

You can restore a deleted project before the clean-up is run.

The <TeamCity Data Directory>/config/_trash/ directory is not cleaned automatically and can be emptied manually if you are sure you do not need the deleted projects.

tip

If you attempt to delete a project with dependent build configurations from other projects, TeamCity will warn you about it. If you proceed with the deletion, the dependencies will no longer function.