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.


Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Use the Administration link in the top right corner to go to the Administration area and click Create project and select Manually.
    Specify the project's name, ID (autogenerated, modifiable) and an optional description. Click Create:

  2. When a project is created, TeamCity prompts to populate it with build configurations. Click Create build configuration. They can be created automatically (similarly to creating projects) or manually as described below. If you select to do it manually, specify the build configuration name, ID (autogenerated, modifiable) and an optional description.  

  3. Next TeamCity offers to create and attach a new VCS Root: to be able to create a build, TeamCity has to know where the source code resides, and a VCS root is a collection of VCS settings (paths to sources, login, password, and other settings) that defines how TeamCity communicates with a version control (SCM) system to monitor changes and get sources for a build. Each build configuration has to have at least one VCS root attached to it. 
    A VCS root can be created automatically or manually. To create it manually, select the type of VCS from the drop-down  (Git in the example below), specify the required information (name and URL), test your connection and click Create. 


    If your project resides in several version control systems, you can attach as many VCS Roots to it as you need. For example, if you store a part of your project in Perforce, and the rest in Git, you need to create and attach 2 VCS roots - one for Perforce, another for Git. Learn more about configuring VCS roots.

    After you have created a VCS root, you can instruct TeamCity to exclude some directories from checkout, or map some paths (copy directories and all their contents) to a location on the build agent different from the default one. 
    This can be done by means of checkout rules. You can also specify whether you want TeamCity to checkout the sources on the agent or server.
    Note that the agent-side checkout is supported not for all VCSs, and in case you want to use it, you need to have a version control client installed on at least one agent.

    After the VCS Root is created, the build configuration settings are displayed on the left.

  4. Now you can configure Build steps by selecting the corresponding setting on the left. You can either instruct TeamCity to automatically detect the build steps after scanning your repository or configure build steps manually as described in this example.
    Click Add build step and select a build runner from the drop-down. 

  5.  Fill in the required fields and save the build stepюstep.
  6. Congratulations! You've configured your first build containing one build step.  Now you can run your build and tweak its settings if necessary.