Supported Platforms and Environments

Edit page

This page covers software-related environments TeamCity works with. For hardware-related notes, see this section.

Platforms (Operating Systems)

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.

note

Since TeamCity 2019.2, 64-bit Amazon Corretto 8 is included in the Windows .exe TeamCity distribution (previously, 32-bit Oracle Java and then AdoptOpenJDK were bundled with the TeamCity Windows distribution). Users of the bundled version of JRE are automatically switched to 64-bit Amazon Corretto on upgrading TeamCity to 2019.2.

Supported Java versions are OpenJDK and Oracle Java 8 (32 or 64 bit), version 8u16 (or 1.8.0_16) or later. We recommend using the latest available version of JDK 8. Experimental Java 11 support is also provided, but we highly recommend using Java 8 instead.
Using 64-bit Java is recommended .

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.

note

Since TeamCity 2019.2, 64-bit Amazon Corretto 8 is included in the Windows .exe TeamCity distribution (previously, 32-bit Oracle Java and then AdoptOpenJDK were bundled with the TeamCity Windows distribution). Users of the bundled version of JRE are automatically switched to 64-bit Amazon Corretto on upgrading TeamCity to 2019.2.

Supported Java versions are OpenJDK and Oracle Java 8 - 11. We recommend using the latest available version of JDK 8 (or 1.8). 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.

Web Browsers

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:

  • Google Chrome

  • Mozilla Firefox

  • Safari under Mac

  • Microsoft Edge

  • Microsoft Internet Explorer 11+. Support for Internet Explorer 10 is discontinued since TeamCity 2018.1.4.

  • Opera 15+

Build Runners

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.11.

  • 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, and 3.5.4.

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

Testing Frameworks

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

  • TestNG 5.3+

  • MSTest 8.x-12.x,14.x, 15.x, 19.x and VSTest are supported by the Visual Studio Tests 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 gc support 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).

  • Perforce (requires a Perforce client installed on the TeamCity server). Check compatibility issues.

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

  • CVS

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

  • 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

Cloud Agents Integration

See also details on the cloud integrations and non-bundled and third-party cloud integration plugins.

VCS Hosting Services Integration

Issue Tracker Integration

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.

IDE Integration

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.

  • Microsoft Visual Studio 2010, 2012, 2013, 2015, 2017 is supported by the TeamCity Visual Studio Add-in shipped as a part of ReSharper Ultimate. Installed .NET Framework is required.

Remote Run and Pre-tested Commit

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

IDE

Supported VCS

Eclipse

  • Subversion 1.7-1.8 via Subclipse and Subversive Eclipse integration plugins or SvnKit.

  • Subversion 1.4-1.7 via Subclipse and Subversive Eclipse integration plugins.

  • Perforce (P4WSAD 2009.2 - 2010.1, P4Eclipse 2010.1 - 2015.1)

  • Git (the EGit 2.0+ Eclipse integration plugin)

  • CVS

  • ClearCase (the client software is required), integrated via an additional plugin

  • see also

IntelliJ IDEA Platform *)

  • Subversion

  • Perforce

  • Git (remote run only)

  • Azure DevOps Server, or formerly Team Foundation Server (since TeamCity 2017.1, the plugin update is required)

Microsoft Visual Studio

  • Subversion 1.4-1.11 (the command-line client is required); note that 1.10-1.11 is supported since ReSharper 2018.3.

  • Azure DevOps Server (formerly Team Foundation Server – supported version 2005 or later). Installed Team Explorer is required.

  • Perforce 2008.2 and later (the command-line client is required).

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

Code Coverage

IDE

Supported Coverage Tool

Eclipse

IDEA and EMMA code coverage

IntelliJ IDEA Platform

IDEA, EMMA and JaCoCo code coverage

Microsoft Visual Studio

JetBrains dotCover coverage. Requires JetBrains dotCover installed in Microsoft Visual Studio

Supported Databases

See more at Setting up an External Database

  • HSQLDB 2.3.2
    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 12.1.0.1)