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

TeamCity 2018.x Documentation

Documentation for Previous Versions

Icon

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

« Previous Version 3 Next »

This section details creating projects via the TeamCity web UI. Other options include the REST API and using TeamCity project configuration in DSL based on the Kotlin language.

On this page:

 

Creating Project

To create a project, use the Administration link at the top right corner and click Create project. The Create project page is displayed.

There are several options to create a project:

 

 

To create a subproject, go to the parent project settings page and create a subproject using one of the available options.

Creating project pointing to repository URL

  1. On the Create project page, select to create project from a repository URL.
  2. 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 add a VCS build trigger.
    • 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. 
  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.
    (info) 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 project from GitHub.com.
    • If you do not have a GitHub connection configured, you will be redirected to the Connections page. Set up the connection as described here, then follow the steps below.
    • If you have a GitHub connection configured, follow the steps below.
  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.
  4. TeamCity will add a VCS build trigger and attempt to auto-detect 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 the Run button to start the build.
    (info) 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 project from Bitbucket Cloud.
    • If you do not have a Bitbucket connection configured, you will be redirected to the Connections page. Set up the connection as described here, then follow the steps below.
    • If you have a Bitbucket connection configured, follow the steps below.
  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.
  4. TeamCity will add a VCS build trigger and attempt to auto-detect 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 the Run button to start the build.
    (info) 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 Visual Studio Team Services

  1. On the Create project page, select to create project from Visual Studio Team Services.
    • If you do not have a Visual Studio Team Services connection configured, you will be redirected to the Connections page. Set up the connection as described here, then follow the steps below.
    • If you have a  Visual Studio Team Services connection configured, follow the steps below.
  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.
  4. TeamCity will add a VCS build trigger and attempt to auto-detect 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 the Run button to start the build.
    (info) 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:

    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.

    Icon

    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.

Managing 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 the more button  next to the project on the parent project settings page. These options are not available for the Root project.

Copying Project

Use the corresponding item from the Actions menu in the top right 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.

Icon

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 since TeamCity 2017.2 and 20 in earlier versions unless you purchased additional Build Agent licenses).

Moving Project

Icon

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 top right 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 top right of the project settings page or the more button  next to the project on the parent project settings page. Please refer to the dedicated page.

Bulk Editing IDs

Icon

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 top right 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

Since TeamCity 10.0,  it is possible to pause triggers for all or selected build configurations of a  project.
Use the corresponding item from the 
Actions menu in the top right of the project settings page or the more button  next to the project on the parent project settings page.

Exporting Project 

Since TeamCity 10.0, it is possible to 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 top right 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 top right 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, etc.) 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 <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. 

 

 

Icon

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.



See also:

 

 

 

 

 

 

 

 

 

 

 

 

 

  • No labels