TeamCity supports Git out of the box. Git source control with Visual Studio Team Services is supported (see authentication notes below).
This page contains description of the Git-specific fields of the VCS root settings.
For common VCS Root properties check the section.
On this page:
- General Settings
- Authentication Settings
- Authenticating to Visual Studio Team Services
- Server Settings
- Agent Settings
- Configuring Git Garbage Collection on Server
- Git LFS
- Internal Properties
- Known Issues
- Development Links
The URL of the remote Git repository used for fetching data from the repository.
The URL of the target remote Git repository used for pushing annotated tags created via VCS labeling build feature to the remote repository. If blank, the fetch URL is used.
Lists the patterns for branch names, required for feature branches support. The matched branches are monitored for changes in addition to the default branch. The syntax is similar to checkout rules:
Use tags as branches
Allows monitoring / checking out git tags as branches making branch specification match tag names as well as branches (e.g.
Defines a way TeamCity reports username for a VCS change. Changing the username style will affect only newly collected changes. Old changes will continue to be stored with the style that was active at the time of collecting changes.
Select whether you want to ignore the submodules, or treat them as a part of the source tree. Submodule repositories should either not require authentication or use the same protocol and accept the same authentication as configured in the VCS root.
Username for tags/merge
A custom username used for labeling.
Branch Matching Rules
- If the branch matches a line without patterns, the line is used.
- If the branch matches several lines with patterns, the best matching line is used.
- If there are several lines with equal matching, the one below takes precedence.
Everything that is matched by the wildcard will be shown as a branch name in the TeamCity interface. For example,
refs/heads/feature1branch, but in the TeamCity interface you'll see only
feature1as a branch name.
The short name of the branch is determined as follows:
- if the line contains no brackets, then full line is used, if there are no patterns or part of line starting with the first pattern-matched character to the last pattern-matched character.
- if the line contains brackets, then part of the line within brackets is used.
When branches are specified here, and if your build configuration has a VCS trigger and a change is found in some branch, TeamCity will trigger a build in this branch.
Supported Git Protocols
The following protocols are supported for Git repository URL:
ssh: (e.g. ssh://git.somwhere.org/repos/test.git, ssh://firstname.lastname@example.orgElse.org/repos/test.git, scp-like syntax: email@example.com:repos/test.git)
- git: (e.g. git://git.kernel.org/pub/scm/git/git.git)
- http: (e.g. http://git.somewhere.org/projects/test.git)
file: (e.g. file:///c:/projects/myproject/.git)
Select this option to clone a repository with anonymous read access.
Specify a valid username (if there is no username in the clone URL; the username specified here overrides the username from the URL) and a password to be used to clone the repository.
Valid only for SSH protocol. A private key must be in the OpenSSH format. Select one of the options from the Private Key list and specify a valid username (if there is no username in the clone URL; the username specified here overrides the username from the URL).
For all the available options to connect to GitHub, please see the comment.
Authenticating to Visual Studio Team Services
If you use Git source control with Visual Studio Team Services, the following options are available to you:
Personal Access Tokens
To use access tokens, you need to create a personal access token in your Visual Studio Team Services account, where you have to set some Code access scope in you repositories and use it when configuring a VCS root.
|Password||Enter your personal access token created earlier|
Required Access Scope
|Git||Code (read) / Code (read and write) for versioned settings|
|Work Items||Work items (read)|
|Commit Status||Code (status)|
Alternate Authentication Credentials
To use the login/password pair authentication, you have to enable alternate credentials in your Visual Studio Team Services account, where you can set a secondary username and password to use when configuring a VCS root.
These are the settings used in case of the server-side checkout.
Convert line-endings to CRLF
Convert line-endings of all text files to CRLF (works as setting
Custom clone directory on server
To interact with the remote git repository, the its bare clone is created on the TeamCity server machine. By default, the cloned repository is placed under
These are the settings used in case of the agent-side checkout.
Note that the agent-side checkout has limited support for SSH. The only supported authentication methods are "Default Private Key" and "Uploaded Private Key" .
If you plan to use the agent-side checkout, you need to have Git 1.6.4+ installed on the agents.
Path to git
Provide the path to a git executable to be used on the agent. When set to
Clean Policy/Clean Files Policy
Specify here when the "git clean" command is to run on the agent, and which files are to be removed.
When enabled (default), TeamCity clones the repository under the agent's
Git executable on the agent
TeamCity needs git command line client version 1.6.4+ on the agent in order to use the agent-side checkout.
The recommended approach is to ensure that the git client is available in PATH of the TeamCity agent and leave the "Path to git" setting in the VCS root blank.
If you only have the git command line on some machines, set "Path to git" setting in the VCS root to the %env.
Instead of adding Git to the agent's PATH, you can set the TEAMCITY_GIT_PATH environment variable (or
env.TEAMCITY_GIT_PATH property in the agent's buildAgent.properties file) to the full path to the git executable.
TEAMCITY_GIT_PATH is not defined, the Git agent plugin tries to detect the installed git on the launch of the agent. It first tries to run git from the following locations:
- for Windows - it tries to run
- C:\Program Files\Git\bin
- C:\Program Files (x86)\Git\bin
- for *nix - it tries to run
If git wasn't found in any of these locations, it tries to run the git accessible via the
PATH environment variable.
If a compatible git (1.6.4+) is found, it is reported in the
TEAMCITY_GIT_PATH environment variable. This variable can be used in the Path to git field in the VCS root settings. As a result, the configuration with such a VCS root will run only on the agents where git was detected or specified in the agent properties.
Configuring Git Garbage Collection on Server
TeamCity maintains a clone on the server for every Git repository it works with, so the process which collects changes in the large Git repository may cause memory problems on the server.
To ensure good performance while working with Git repositories, Git garbage collection needs to be configured: besides removing unreferenced objects from the repository, git gc also "defragments" some files under
.git directory, which decreases memory usage on TeamCity server and increases performance. There's a feature request for automatic git gc, but at the moment you need to configure it manually.
To configure Git garbage collection:
- Install native git on the server machine.
- Define the following internal properties:
teamcity.server.git.executable.path=<path to git executale on the TeamCity server machine>
- (Optional) By default, TeamCity executes Git garbage collection until the total time doesn't exceed 60 minutes quota; the quota can be changed using the
- (Optional) By default, Git garbage collection is executed every night at 2 a.m., this can be changed by specifying the internal property with a cron expression like this:
teamcity.git.cleanupCron=0 0 2 * * ? *
- Restart the server for the properties to take effect.
When Git gc is configured, TeamCity will run automatically in the background it for all currently monitored VCS roots.
Starting with 10.0 TeamCity supports Git LFS for agent-side checkout. To use it, install git 1.8.5+ and Git LFS on the build agent machine. Git LFS should be enabled using the 'git lfs install' command. More information on Git LFS can be found in Git LFS documentation.
For Git VCS it is possible to configure the following internal properties:
The idle timeout for communication with the remote repository. If no data were sent or received during this timeout, the plugin throws a timeout error to prevent hanging of the process forever.
(deprecated) Override of "teamcity.git.idle.timeout.seconds" for git fetch operation
Defines whether TeamCity runs git fetch in a separate process
The value of the JVM -Xmx parameter for a separate fetch process
When fetch in a separate process is used, it makes thread-dumps of itself and stores them under
Whether TeamCity should run
The path to the native git executable on the server
Maximum amount of time to run
0 0 2 * * ? *
Cron expression for the time of a cleanup in git-plugin, by default - daily at 2a.m.
Threshold in megabytes after which JGit uses streams to inflate objects. Increase it if you have large binary files in the repository and see symptoms described in TW-14947
Git-plugin builds patches in a separate process, set it to false to build patch in the server process. To build patch git-plugin has to read repository files into memory. To not run out of memory git-plugin reads only objects of size smaller than the threshold, for larger objects streams are used and they can be slow (TW-14947). With patch building in a separate process all objects are read into memory. Patch process uses the memory settings of the separate fetch process.
The number of days after which an unused clone of the repository will be removed from the server machine. The repository is considered unused if there were no TeamCity operations on this repository, like checking for changes or getting the current version. These operations are quite frequent, so 7 days is a reasonably high value.
Defines whether to log additional debug info on each found commit
Type of ssh proxy, supported values: http, socks4, socks5. Please keep in mind that socks4 proxy cannot resolve remote host names, so if you get an UnknownHostException, either switch to socks5 or add an entry for your git server into the hosts file on the TeamCity server machine.
Ssh proxy host
Ssh proxy port
Number of attempts to establish connection to the remote host for testing connection and getting a current repository state before admitting a failure
Interval in seconds between connection attempts
Agent configuration for Git:
When checkout on agent: whether TeamCity should use native SSH implementation.
The idle timeout for the git fetch operation when the agent-side checkout is used. The fetch is terminated if there is no output from the fetch process during this time. Prior to 8.0.4 the default was 600.
When using checkout on an agent, a limited subset of checkout rules is supported. Since TeamCity 10.0, git-plugin translates some of the checkout rules to the sparse checkout patterns. Only the rules which do not remap files are supported:
An unsupported rule example is
- java.lang.OutOfMemoryError while fetch repository. Usually occurs when there are large files in the repository. By default, TeamCity runs fetch in a separate process. To run fetch in the server process, set the
teamcity.git.fetch.separate.processinternal property to
- Teamcity run as a Windows service cannot access a network mapped drives, so you cannot work with git repositories located on such drives. To make this work, run TeamCity using teamcity-server.bat.
- inflation using streams in JGit prevents
OutOfMemoryError, but can be time-consuming (see the related thread at jgit-dev for details and the TW-14947 issue related to the problem). If you meet conditions similar to those described in the issue, try to increase
teamcity.git.stream.file.threshold.mb. Additionally, it is recommended to increase the overall amount of memory dedicated for TeamCity to prevent
Git support is implemented as an open-source plugin. For development links, refer to the plugin's page.