Find a tool for you
Whichever technologies you use there's a JetBrains tool to match
find a tool
Ides
AppCode CLion Datalore DataGrip GoLand IntelliJ IDEA PhpStorm PyCharm Rider RubyMine WebStorm
.NET & Visual Studio
ReSharper Rider ReSharper C++ dotCover dotMemory dotPeek dotTrace
Team Tools
TeamCity Upsource YouTrack Hub
Education
PyCharm Edu IntelliJ IDEA Edu JB Academy
Toolbox App A control panel for your tools and projects
Kotlin Programming language
for JVM & Android MPS Create your own domain-specific language
C++ Tools Tools for C/C++ development
for any platform For Business Wide range of tools.
All major technologies covered
Game Development Tools for game development
for any platform DevOps Tools and integrations
for any infrastructure
Education Products to learn and teach programming
JetBrains Store
Pricing and licensing for businesses and individuals
visit store
Customers
Sales Support Orders, payments Product Support Tech support, documentation
Community Programs
Education Students, classrooms, training Open Source Projects support Sponsorship User groups, events, technology experts
Resources
Newsletters Webinars Early Access Blog
Initiatives
Open Source Projects, contributions Research Scientific, marketing research
Company
About People, customers, awards Brand Assets Guidelines, logos Careers Jobs, internships Contacts Partners, resellers, Kotlin training
TeamCity
Get TeamCity

VCS Interoperability

TeamCity version controls systems integration is comprehensive. It’s hard to imagine a project whose source code couldn’t be retrieved by TeamCity.

Flexible VCS Configuration

TeamCity supports a broad range of version controls out of the box, from the most popular ones to somewhat deprecated but still used systems.

For a single build TeamCity can take source code from several different VCS repositories. You can even mix different types of VCS.

Suppose the majority of your project sources is located in Perforce while several modules are stored in Subversion. TeamCity allows you to configure your project to use sources from both of them simultaneously.

Multiple VCS roots

Storing Project Settings in VCS

TeamCity provides the two-way synchronization of project settings with the version control the same way it is done with the source code. Synchronization is supported for Git, Mercurial, Perforce, Subversion, and TFS. You can enable synchronization on the Versioned Settings page of the project administration.

Feature branches

Developing with feature branches in Git and Mercurial with TeamCity is extremely simple. Just tell TeamCity which branch names to monitor.

Feature Branches

As soon as you push your branch to Git, Mercurial repository or to Perforce stream, TeamCity will detect it and start a build on your changes.

TeamCity Feature Branches with Git

You can configure TeamCity to merge a feature branch automatically to the master if a build in the feature branch completes successfully, or if no new tests failed in this branch.

File Diff and Patches

View file differences in TeamCity’s web interface, or download a patch from TeamCity right in your IDE.

GitHub Pull Requests

Filter the GitHub pull requests by author and limit them to internal or external collaborators, or open them for everyone. There is also the option to filter pull requests by target branch.

Build GitHub Pull Requests

The Pull Requests support is also available for GitLab merge requests and BitBucket server.

Enhanced Mercurial Support

TeamCity fully supports Mercurial’s bookmarks and subrepositories. The former could be used as feature branches. From the latter TeamCity gathers and shows changes.

Mercurial Sub-repository support in TeamCity 8

Advanced VCS build triggering

Advanced VCS build triggering

TeamCity constantly scans all of the build configurations’ VCS roots, and triggers builds if changes are found.
You can configure multiple options for fine-grained control of triggering rules.

VCS Trigger