Supported Platforms and Environments
This page covers software-related environments TeamCity works with. For hardware-related notes, see this section.
Platforms (Operating Systems)
Core features of TeamCity server are platform-independent. See considerations on choosing server platform.
The TeamCity server is a web application that runs within a capable J2EE servlet container.
The server requires a Java SE JRE installation to run. See notes on how to install Java on the server.
Supported Java versions are OpenJDK and Oracle Java 8 (8u16 or later) and 11 (32 or 64 bit). Using 64-bit Java is recommended.
The TeamCity server Windows installer and server Docker images come bundled with 64-bit Java 11.
Generally, all the recent versions of Windows, Linux, and macOS are supported. If you find any compatibility issues with any of the operating systems, make sure to let us know.
The TeamCity server is tested under the following operating systems:
Linux (Ubuntu, Debian, RedHat, SUSE, and others)
Windows Server 2008, 2012, 2016, 2019
Server Core installation of Windows Server 2016
Windows 10 under the Tomcat 8.5+ web application server.
Reportedly works without known issues on:
Windows Server 2008 R2
Note that Windows XP/XP x64 are not supported.
The TeamCity Agent is a standalone Java application.
Build agents require a Java SE JRE installation to run. See notes on how to configure Java on agents.
Supported Java versions are OpenJDK and Oracle Java 8 - 11. We recommend using the latest available version of JDK. Support for running agents under Java 1.6 and 1.7 is deprecated.
The TeamCity agent is tested under the following operating systems:
Windows Server 2003/2008, 2012, 2016, 2019
Server Core installation of Windows Server 2016
Reportedly works on:
Windows XP/XP x64
Windows 2000 (interactive mode only)
Windows Tray Notifier
Windows 7/7x64/10 with one of the supported versions of Internet Explorer.
The TeamCity Web Interface is mostly W3C-compliant, so just about any modern browser should work well with TeamCity. The following browsers have been specifically tested and reported to work correctly in the recent versions of:
Safari under Mac
TeamCity supports a wide range of build tools, enabling both Java and .NET software teams to build their projects.
Supported Java build runners
Ant 1.6-1.10. TeamCity comes bundled with Ant 1.9.14.
Maven versions 2.0.x, 2.x, 3.x (known at the moment of the TeamCity release). Java 1.5 and higher is supported. TeamCity comes bundled with Maven 2.2.1, 3.0.5, 3.1.1, 3.2.5, 3.3.9, 3.5.4, and 3.6.3.
IntelliJ IDEA Project runner (requires Java 8)
Gradle (requires Gradle 0.9-rc-1 or higher)
Supported .NET platform build runners
MSBuild. Requires .NET Framework or Mono installed on the build agent. Microsoft Build Tools 2013, 2015, 2017, and 2019 are also supported.
NAnt versions 0.85 - 0.91 alpha 2. Requires .NET Framework or Mono installed on the build agent.
FxCop. Requires FxCop installed on the build agent.
Duplicates Finder for C# and VB.NET code based on ReSharper Command Line Tools. Supported languages are C# up to version 4.0 and VB.NET version 8.0 - 10.0. Requires .NET Framework 4.6.1+ installed on the build agent.
.NET Process Runner for running any .NET application (requires .NET installed on the build agent)
- NuGet runners under Windows, Linux, macOS. Require NuGet.exe Command Line tool installed on the agents. Supported NuGet versions under Windows are 1.4+.
Windows: NuGet versions prior to 2.8.6 require .NET Framework 4.0+ installed on the build agent
Windows: NuGet 2.8.6 and later requires .NET 4.5
Linux and macOS: require Mono 4.4.2+ and NuGet CLI 3.2+ installed on the agent
JUnit 3.8.1+, 4.x
NUnit 2.2.10, 2.4.x, 2.5.x, 2.6.x, 3.0.x are supported (dedicated build runner).
MSTest 8.x-12.x, 14.x, 15.x, 19.x and VSTest are supported by the .NET runner; requires the appropriate Microsoft Visual Studio edition or Visual Studio Test Agent installed on the build agent.
MSpec (requires MSpec installed on the build agent)
Version Control Systems
Git (for automatic
git gcsupport requires Git client installed on the server in order to perform maintenance of Git clones, latest version is recommended)
Subversion (server versions 1.4-1.9 and higher as long as the protocol is backward-compatible).
Team Foundation Server 2005, 2008, 2010, 2012, 2013, 2015, 2017 are supported.
Mercurial (requires the Mercurial "hg" client v1.5.2+ installed on the server)
SourceGear Vault 6 and 7 (requires the Vault command line client libraries installed on the TeamCity server), integrated via an additional plugin
Borland StarTeam 6 and up (the StarTeam client application must be installed on the TeamCity server)
IBM Rational ClearCase Base and UCM modes (requires the ClearCase client installed and configured on the TeamCity server), integrated via an additional plugin
Microsoft Visual SourceSafe 6 and 2005 (requires a SourceSafe client installed on the TeamCity server, available only on Windows platforms)
For support for other VCS please check external plugins available.
Checkout on Agent
The requirements noted are for agent environment and are additional to those for the server listed above.
Git (git client version 1.6.4+ must be installed on the agent, latest version is recommended)
Subversion (working copies in the Subversion 1.4-1.8 format are supported)
Perforce (a Perforce client must be installed on the TeamCity agent machine)
Team Foundation Server 2005-2015, 2017 are supported.
Mercurial (the Mercurial "hg" client v1.5.2+ must be installed on the TeamCity agent machine)
IBM Rational ClearCase (the ClearCase client must be installed on the TeamCity agent machine)
Labeling Build Sources
Team Foundation Server
SourceGear Vault, integrated via an additional plugin
ClearCase, integrated via an additional plugin
Remote Run on Branch
VCS Systems Supported via Third Party Plugins
Cloud Agents Integration
VCS Hosting Services Integration
Issue Tracker Integration
JetBrains YouTrack 1.0 and later (tested with the latest version)
Atlassian Jira 4.4 and later (all major features also reportedly worked for version 4.2)
Bugzilla 3.0 and later (tested with Bugzilla 5.0.1)
Azure DevOps Server (formerly Visual Studio Team Foundation Server — supported version 2012 or later, and Azure DevOps Services are supported)
Additional requirements are listed in Integrating TeamCity with Issue Tracker.
Links to issues of any issue tracker can also be recognized in change comments using Mapping External Links in Comments.
TeamCity provides productivity plugins for the following IDEs:
Eclipse: Eclipse versions 3.8 and 4.2-4.6 are supported. Eclipse must be run under JDK 1.5+
IntelliJ Platform Plugin: compatible with IntelliJ IDEA 15.0.x - 2019.3.x (Ultimate and Community editions); as well as other IDEs based on the same version of the platform, including JetBrains RubyMine 6.3+, JetBrains PyCharm 3.1+, JetBrains PhpStorm/WebStorm 7.1+, AppCode 2.1+. See more information on compatibility.
Remote Run and Pre-tested Commit
*) Supported only with the VCS integrations bundled with the IDEs by JetBrains
See more at Setting up an External Database
The internal database suits evaluation purposes only; we strongly recommend using an external database in a production environment.
MySQL 5.0.33+, 5.1.49+, 5.5+, 5.6+, 5.7+, 8+ (Note that due to bugs in MySQL, versions 5.0.20, 5.0.22 and 5.1 up to 5.1.48 are not compatible with TeamCity)
Microsoft SQL Server 2005 or later (including Express editions), SQL Azure; SSL connections support might require these updates.
PostgreSQL 8.2 and newer
Oracle 10g and newer (TeamCity is tested with driver version 220.127.116.11)