Supported Platforms and Environments
This page covers software-related environments TeamCity works with. For hardware-related notes, see this section.
TeamCity Server is a web application that runs within a capable J2EE servlet container. It requires a Java SE JRE installation to run. See notes on how to install Java on a TeamCity server.
Supported Java versions: OpenJDK and Oracle Java 8 (8u16 or later), 11, and 17 (32 or 64 bit). Using 64-bit Java is recommended.
The TeamCity server Windows installer and server Docker images come bundled with Amazon Corretto 64-bit Java 17.
For Apple ARM systems (for example, Apple M1 or M2), consider using a different version of Java, like Azul OpenJDK.
warning
Java 8 support will be discontinued in one of the future TeamCity Server versions. If you use a non-bundled version of Java 8, we highly recommend that you migrate your server to Java 11 or 17.
tip
The core features of TeamCity Server are platform-independent. See considerations on choosing the server platform.
Generally, all the recent versions of Windows, Linux, and macOS are supported. If you find any compatibility issues with any of the operating systems, let us know.
TeamCity Server is tested under the following operating systems:
Linux (Ubuntu, Debian, RedHat, SUSE, and others)
macOS
Windows 7/7x64
Windows Server 2008, 2012, 2016, 2019, 2022
Server Core installation of Windows Server 2016
Windows 10 and 11 under the Tomcat 8.5+ web application server
Reportedly works without known issues on:
Windows 7+
Windows Server 2008 R2
Solaris
FreeBSD
IBM z/OS
HP-UX
Windows XP/XP x64 are not supported.
Regarding architectural compatibility, TeamCity is not limited to any specific list. The verified and thoroughly tested architectures include:
Intel x86
AMD64 (x86_64)
Apple Silicon (M chips)
Amazon ARM (Graviton)
If you are using a different architecture that is not explicitly mentioned above, you may expect the TeamCity server to support it, provided that your operating system is supported and a suitable Java Virtual Machine (JVM) option exists.
TeamCity Agent is a standalone Java application. It requires a Java SE JRE installation to run. See notes on how to configure Java on agents.
Supported Java versions: OpenJDK and Oracle Java 8-17. We recommend using the latest available version of JDK.
The TeamCity agent Windows installer and agent Docker images come bundled with Amazon Corretto 64-bit Java 17.
For Apple ARM systems (for example, Apple M1 or M2), consider using a different version of Java 17, like Azul OpenJDK.
note
Note that Java versions specified in this section are requirements to run the agent itself. Builds can utilize other versions installed on agent machines (for example, JDK 19).
TeamCity Agent is tested under the following operating systems:
Linux
macOS
Windows 7/7x64
Windows 10
Windows Server 2003/2008, 2012, 2016, 2019, 2022
Server Core installation of Windows Server 2016
Reportedly works on:
Windows XP/XP x64
Windows 2000 (interactive mode only)
Solaris
FreeBSD
IBM z/OS
HP-UX
Regarding architectural compatibility, TeamCity is not limited to any specific list. The verified and thoroughly tested architectures include:
Intel x86
AMD64 (x86_64)
Apple Silicon (M chips)
Amazon ARM (Graviton)
If you are using a different architecture that is not explicitly mentioned above, you may expect the TeamCity Agent to run on it, provided that your operating system is supported and a suitable Java Virtual Machine (JVM) option exists.
The TeamCity web interface is mostly W3C-compliant, so any modern browser should work well with TeamCity. The recent versions of the following browsers have been specifically tested and reported to work correctly:
Google Chrome
Mozilla Firefox
Safari under macOS
Microsoft Edge
Opera
Runner | Supported versions | Bundled versions |
|---|---|---|
1.6-1.10 | 1.10.10 | |
2.0.x, 2.x, 3.x | 2.2.1, 3.0.5, 3.1.1, 3.2.5, 3.3.9, 3.5.4, 3.6.3, 3.8.6 | |
0.9-rc-1 or later | ||
We recommend that you use the unified .NET runner to run .NET projects in TeamCity. See its requirements here.
Other .NET runners:
Runner | Supported versions | Requirements |
|---|---|---|
.NET 6.0 or later | .NET 6.0 or later installed on the build agent, or can be run inside a Docker container with .NET 6.0 or later | |
Microsoft Build Tools 2013, 2015, 2017, 2019 | .NET Framework or Mono installed on the build agent | |
0.85 - 0.91 alpha 2 | .NET Framework or Mono installed on the build agent | |
A corresponding version of Microsoft Visual Studio installed on the build agent | ||
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 | .NET Framework 4.6.1 or later installed on the build agent |
.NET Framework 4.6.1 or later installed on the build agent | ||
.NET installed on the build agent | ||
NuGet 1.4 or later | Required on the build agent:
|
Runner | Supported versions | Requirements |
|---|---|---|
2.0 or later | Python installed on the build agent | |
0.7.3 gem or later | ||
1.0 - 5.0 | ||
3-13 | Xcode installed on the build agent |
Framework | Supported versions | Requirements |
|---|---|---|
JUnit | 3.8.1+, 4.x | |
2.2.10, 2.4.x, 2.5.x, 2.6.x, 3.0.x | ||
TestNG | 5.3 or later | |
MSTest and VSTest | 8.x-12.x, 14.x, 15.x, 19.x are supported by the .NET runner | A corresponding Microsoft Visual Studio edition or Visual Studio Test Agent installed on the build agent |
MSpec installed on the build agent |
Read more about the support for testing frameworks in TeamCity.
VCS | Supported versions | Requirements |
|---|---|---|
For automatic | ||
Server versions 1.4-1.9 or later | ||
A Perforce Helix Core client installed on the server (2017.1+ versions are supported). | ||
2005, 2008, 2010, 2012, 2013, 2015, 2017 | ||
A Mercurial "hg" client v1.5.2+ installed on the server | ||
CVS (via an external plugin) | ||
6 or later | A StarTeam client application installed on the server |
Other VCSs can be supported in TeamCity via external plugins.
VCS | Supported versions | Requirements |
|---|---|---|
1.6.4 or later | A Git client installed on the agent | |
1.4-1.8 | ||
A Perforce client installed on the agent | ||
2005-2015, 2017 | ||
A Mercurial "hg" client v1.5.2+ installed on the agent | ||
Git
Subversion
Perforce
Azure DevOps
Mercurial
CVS
Borland StarTeam
Git
Mercurial
Git
Mercurial
Azure DevOps Services, or formerly Visual Studio Team Services
The following cloud platforms can be used to run build agents:
Available as non-bundled plugins:
Tracker | Supported versions |
|---|---|
1.0 or later | |
4.4 or later (all major features also reportedly worked for version 4.2) | |
3.0 or later | |
0.9-rc-1 or later | |
Azure DevOps Server (formerly Team Foundation Server — supported version 2012 or later), and Azure DevOps Services |
See also additional requirements.
TeamCity provides productivity plugins for the following IDEs:
IDE | Supported versions | Requirements |
|---|---|---|
Compatible with IntelliJ IDEA 2019.3 - 2021.2.3 (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. | ||
2010, 2012, 2013, 2015, 2017, 2019 | .NET Framework |
Remote Run and Pre-tested commit functionality is available for the following IDEs and version control systems:
IDE | Supported VCS |
|---|---|
(supported only for VCS integrations bundled with JetBrains IDEs) |
|
|
IDE | Supported Coverage Tools |
|---|---|
JetBrains dotCover coverage. Requires JetBrains dotCover installed in Microsoft Visual Studio. |
Database | Supported versions |
|---|---|
HSQLDB (The internal HSQLDB database can be used for evaluation purposes only.) | 2.3.2 |
MySQL | 5.7.34 or later |
Microsoft SQL Server | 2012 or later (including Express editions), SQL Azure |
PostgreSQL | 9.6 or later |
Oracle | 10g or later (tested with the driver version 12.1.0.1 |
Unity, by the means of the Unity Support plugin (bundled in TeamCity Cloud and can be installed on-demand in TeamCity On-Premises)