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:

(warning) TeamCity with the native MSSQL external database driver is not compatible with Oracle Java 6 Update 29, due to a bug in Java itself. You can use earlier or later versions of Oracle Java.

Generally, all the recent versions of Windows, Linux and Mac OS X 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:

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 2000/XP/Vista/Vista x64/7/7x64/8/10 with one of the supported versions of Internet Explorer.

Web Browsers

The TeamCity Web Interface is 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:

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

Using server-side checkout mode does not impose any additional requirements for agent environment.

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

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.4-1.7 with Subclipse and Subversive Eclipse integration plugins.
  • Subversion 1.7-1.8 via Subversive/Subclipse/SvnKit.
  • Perforce (P4WSAD 2008.1 - 2010.1, P4Eclipse 2010.1 - 2014.1)
  • ClearCase (the client software is required)
  • CVS
  • Git (the EGit 1.0+ Eclipse integration plugin)
    see also

IntelliJ IDEA Platform

  • ClearCase
  • Git (remote run only)
  • Perforce
  • StarTeam
  • Subversion
  • Visual SourceSafe

Microsoft Visual Studio

  • Subversion 1.4-1.8. Since TeamCity 9.1.5, Subversion 1.9 is supported (by the Addin in the ReSharper Ultimate 10.0.2.). 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)

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