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

In this section:

Platforms (Operating Systems)

TeamCity Server

Core features of TeamCity server are platform-independent. See considerations on choosing server platform.
TeamCity server is a web application that runs within a capable J2EE servlet container.

Requirements:

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

Generally, all the recent versions of Windows, Linux and macOS are supported. If you find any compatibility issues with any of the operating systems please make sure to let us know.

The TeamCity server is tested under the following operating systems:

Reportedly works without known issues on:

Note that Windows XP/XP x64 are not supported.

Build Agents

The TeamCity Agent is a standalone Java application.

Requirements:

TeamCity agent is tested under the following operating systems:

Reportedly works on:

Stop Build Functionality

Build stopping is supported on:

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:

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

Supported .Net platform build runners

Other runners

Testing Frameworks

Version Control Systems

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.

Labeling Build Sources

Remote Run on Branch

Feature Branches

VCS Systems Supported via Third Party Plugins

Cloud Agents Integration

Check also other non-bundled and third-party cloud integration plugins.

VCS Hosting Services Integration

Issue Tracker Integration

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:

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

IntelliJ IDEA Platform *)

  • Subversion
  • Perforce
  • Git (remote run only)
  • Team Foundation Server (since TeamCity 2017.1; the plugin update is required)
  • ClearCase

Microsoft Visual Studio

  • Subversion 1.4-1.9 (the command-line client is required)
  • Team Foundation Server 2005 and 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