Configuring VCS Settings

Skip to end of metadata
Go to start of metadata
Search

Searching TeamCity 7.x Documentation

Table of Contents

A Version Control System (VCS) is a system for tracking the revisions of the project source files. It is also known as SCM (source code management) or a revision control system. The following VCSs are supported by TeamCity out-of-the-box: ClearCase, CVS, Git, Mercurial, Perforce, StarTeam, Subversion, Team Foundation Server, SourceGear Vault, Visual SourceSafe.

Setting up VCS parameters is one of the mandatory steps during creating a build configuration in TeamCity.
On the 2nd page of the build configuration (Version Control Settings page) do the following :

  1. Attach an existing VCS root to your build configuration, or create a new one to be attached. This is the main part of VCS parameters setup; a VCS Root is a description of a version control system where project sources are located. Learn more about VCS Roots and configuration details here.
  2. When VCS root is attached, specify the checkout rules for it — specifying checkout rules provides advanced possibilities to control sources checkout. With the rules you can exclude and/or map paths to a different location on the Build Agent during checkout.
  3. Define how project sources reach an agent via VCS Checkout Mode.
  4. Additionally, you can add a label into the version control system for the sources used for a particular build by means of VCS Labeling feature.



See also:

Administrator's Guide: Configuring VCS Roots | VCS Checkout Rules | VCS Checkout Mode | VCS Labeling

Labels:

configure configure Delete
rule rule Delete
vcs vcs Delete
root root Delete
label label Delete
labeling labeling Delete
notification notification Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.