Supported Platforms and Environments

TeamCity Server

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.

Note that the .war distribution is going to be discontinued, and it is highly recommended using the .tar.gz distribution which has Tomcat web server bundled. It is not advised to customize Tomcat settings unless absolutely necessary.
If you still want to use the .war distribution, note that:

• TeamCity is tested only under Apache Tomcat 8.5+, earlier Tomcat versions are not supported.

• TeamCity is meant to support J2EE Servlet 3.0+ and JSP 2.2+ container based on Apache Jasper.

• TeamCity may not work properly if the Apache Portable Runtime is enabled in Tomcat due to the issues in APR.

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)

• macOS

• Windows 7/7x64

• 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 7+

• Windows Server 2008 R2

• Solaris

• FreeBSD

• IBM z/OS

• HP-UX

Note that Windows XP/XP x64 are not supported.

Build Agents

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:

• Linux

• macOS

• Windows 7/7x64

• Windows 10

• 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)

• Solaris

• FreeBSD

• IBM z/OS

• HP-UX

Windows Tray Notifier

Windows 7/7x64/10 with one of the supported versions of Internet Explorer.

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)

• Java Inspections and Java Duplicates based on IntelliJ IDEA (requires Java 8)

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.

• Microsoft Visual Studio Solutions (2003- 2015, 2017, and 2019). Requires a corresponding version of Microsoft Visual Studio 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.

• Inspections for .NET based on ReSharper Command Line Tools. 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

• .NET CLI (dotnet). Requires the .NET Core SDK installed on build agents.

Other runners

• Rake

• Command Line Runner for running any build process using a shell script

• PowerShell versions 1.0 through 5.0 are supported.

• Xcode versions 3-8 are supported (requires Xcode installed on the build agent)

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)

• CVS

• IBM Rational ClearCase (the ClearCase client must be installed on the TeamCity agent machine)

Labeling Build Sources

• Git

• Subversion

• Perforce

• Team Foundation Server

• Mercurial

• CVS

• SourceGear Vault, integrated via an additional plugin

• Borland StarTeam

• ClearCase, integrated via an additional plugin

Remote Run on Branch

• Git

• Mercurial

Feature Branches

• Git

• Mercurial

VCS Systems Supported via Third Party Plugins

• AccuRev
• Bazaar

• PlasticSCM (related details)

Remote Run and Pre-tested Commit

Remote Run and Pre-tested commit functionality is available for the following IDEs and version control systems:

*) Supported only with the VCS integrations bundled with the IDEs by JetBrains

Code Coverage