TeamCity 9.0 Help

Creating and Editing Projects

Create project

To create a new project: On the Administration | Projects page select one of the options:

To create a subproject, go to the parent project settings page and create a subproject manually or automatically from a URL.

Create Project from URL

  1. Click the Create project from URL button.

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

    Setting

    Description

    Parent Project

    Select the parent project form the drop-down.

    Repository URL

    A VCS repository URL. TeamCity recognizes URLs for Subversion, Git and Mercurial. TFS and Perforce are partially supported.

    Username

    Provide username if access to repository requires authentication

    Password

    Provide username if access to repository requires authentication

  3. Click Proceed.

TeamCity will configure the rest of settings for you.

  • it will determine the type of the VCS repository, auto-configure VCS repository settings, and suggest the project and build configuration names:

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

  • TeamCity will attempt to auto-detect build steps: Ant, NAnt, Gradle, Maven, MSBuild, Visual Studio solution files, PowerShell, Xcode project files, Rake, and IntelliJ IDEA projects. If none found, you will have to configure build steps manually.

  • Next, TeamCity will suggest build triggers, failure conditions and build features. Depending on the build configuration settings, it can suggest some additional configuration options.

Create Project

  1. Click the Create Project button.

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

    Setting

    Description

    Parent Project

    Select the parent project form the drop-down.

    Name

    The project name.

    Project ID

    the ID of the project

    Description

    Optional description for the project.

  3. Click Create. An empty project is created.

  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.

Manage Project

You can view all available projects and subprojects on the Projects Overview page listed in alphabetical order by default. Starting from TeamCity 9.1., administrators can customize the default order.

To copy, move, delete or archive a project, use the Actions menu in the top right of the project settings page or More menu next to the project on the Root project settings page. These options are not available for the Root project.

Copy Project

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.

Move Project

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

Archive Project

Please refer to the dedicated page.

Delete Project

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 (24 hours 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. You can restore a deleted project before the clean-up is run.

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

Last modified: 20 April 2023