Supported Platforms and Environments

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

Platforms (Operating Systems)

TeamCity Server

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

Requirements:

• Java (JRE)

  • Oracle Java 6-8, (Java 7 is included in the Windows .exe distribution).

  • OpenJDK 7 is supported.

  • Both 32-bit and 64-bit Java versions can be Installing and Configuring the TeamCity Server.

• For .war distribution: J2EE Servlet (2.5+) container, JSP 2.0+ container based on Apache Jasper. TeamCity is tested under Tomcat 7 which is the recommended server. Tomcat 7 (Since TeamCity 8.1.5, Tomcat 7.0.55) is already included in Windows .exe and .tar.gz distributions. TeamCity is reported to work with Jetty and Tomcat 6.x-7.x. It is highly recommended to use the .tar.gz distribution (which has Tomcat bundled) and not to customize Tomcat settings unless absolutely necessary. If you still want to use the .war distribution, note that

  • it is recommended to use Tomcat 6.0.35+; earlier versions of Tomcat have some issues which can cause a deadlock in TeamCity on the start-up.

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

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.

The TeamCity server is tested under the following operating systems:

• Linux (Ubuntu, Debian, RedHat, SUSE, and others)

• MacOS X

• Windows XP

• Windows Vista/Windows Vista 64

• Windows 7/7x64

• Windows Server 2008

• Windows 8 under the Tomcat 7 web application server.

Reportedly works on:

• Windows Server 2008 R2

• Windows Server 2012

• Solaris

• FreeBSD

• IBM z/OS

• HP-UX

Build Agents

The TeamCity Agent is a standalone Java application.

Requirements:

• Java (JRE)

  • Oracle Java 6-8, (Java 7 is included in the Windows .exe distribution).

  • OpenJDK 7 is supported.

  • Both 32-bit and 64-bit Java versions can be Setting up and Running Additional Build Agents.

TeamCity agent is tested under the following operating systems:

• Linux

• MacOS X

• Windows XP/XP x64/Vista/Vista x64

• Windows 7/7x64 (recommended choice for Windows installations)

• Windows 8

• Windows Server 2003/2008

Reportedly works on:

• Windows Server 2012

• Windows 2000 (interactive mode only)

• Solaris

• FreeBSD

• IBM z/OS

• HP-UX

Stop Build Functionality

Build stopping is supported on:

• Windows 2000/XP/XP x64/Vista/Vista x64/7/7x64/8

• Linux on x86, x64, PPC and PPC64 processors

• Mac OS X on Intel and PPC processors

• Solaris 10 on x86, x64 processors

Windows Tray Notifier

Windows 2000/XP/Vista/Vista x64/7/7x64/8 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:

• Microsoft Internet Explorer 7+ (without the compatibility mode)

• Mozilla Firefox 3.6+

• Opera 9.5+

• Safari 3+ under Mac/Windows

• Google Chrome

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.9 (TeamCity comes bundled with Ant 1.8.2, since TeamCity 8.1, Ant 1.8.4)

• 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 and Maven 3.0.5. Since TeamCity 8.1, Maven 3.1)

• IntelliJ IDEA project runner

• Gradle (requires Gradle 0.9-rc-1 or higher)

• Inspections and Duplicates Finder (Java) based on IntelliJ IDEA (requires Java 1.6+)

Supported .Net platform build runners

• MSBuild (requires .Net Framework or Mono installed on the build agent. Since TeamCity 8.0.5 Microsoft Build Tools 2013 are also supported.)

• NAnt versions 0.85 - 0.91 alpha 2 (requires .Net Framework or Mono installed on the build agent)

• Visual Studio (sln) (Visual Studio 2003, 2005, 2008, 2010, 2012, and since TeamCity 8.0.5, 2013) (requires a corresponding version of Microsoft Visual Studio installed on the build agent)

• FxCop (requires FxCop installed on the build agent)

• Duplicates Finder (.NET) 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.0+ installed on the build agent. Since TeamCity 8.0.6 Microsoft Visual Studio 2013 solutions are supported.

• Inspections (.NET) based on ReSharper Command Line Tools. Requires .Net Framework 4.0+ installed on the build agent. Since TeamCity 8.0.6 Microsoft Visual Studio 2013 solutions are supported.

• NuGet runners (supported only for agents running Windows OS. Require NuGet.exe Command Line tool installed on the agents). Supported NuGet versions are 1.4+.

Other runners

• Rake

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

• PowerShell

• .NET Process runner for running any .NET application (requires .NET installed on the build agent0

• Xcode Project 3 and 4. Since TeamCity 8.1 Xcode 5 and 6 are supported. (requires Xcode installed on the build agent.)

• JUnit 3.8.1+, 4.x

• NUnit Support 2.2.10, 2.4.x, 2.5.x, 2.6.x (dedicated build runner)

• TestNG 5.3+

• MSTest Support 8.x, 9.x, 10.x, 11.x, and (since TeamCity 8.1) 12.x. (the dedicated build runner; requires appropriate Microsoft Visual Studio edition installed on the build agent)

• MSpec (requires MSpec installed on the build agent)

Version Control Systems

• Subversion (server versions 1.4-1.7 and higher as long as the protocol is backward compatible). Check TeamCity Subversion 1.8 support.

• Perforce (requires a Perforce client installed on the TeamCity server) Check Perforce VCS Compatibility.

• Git (JetBrains) (requires a Git client installed on the TeamCity server).

• Mercurial (requires the Mercurial "hg" client v1.5.2+ installed on the server)

• Team Foundation Server 2005, 2008, 2010, 2012, and (since TeamCity 8.0.6) 2013. Requires Team Explorer installed on the TeamCity server, available only on Windows platforms.

• CVS

• IBM Rational ClearCase, Base and UCM modes (requires the ClearCase client installed and configured on the TeamCity server)

• SourceGear Vault 6 and 7 (requires the Vault command line client libraries installed on the TeamCity server)

• Visual SourceSafe 6 and 2005 (requires a SourceSafe client installed on the TeamCity server, available only on Windows platforms)

• StarTeam 6 and up (the StarTeam client application must be installed on the TeamCity server)

Checkout on Agent

The requirements noted are additional to those listed above.

• Subversion (working copies in the Subversion 1.4-1.7 format are supported)

• CVS

• Git (git v.1.6.4+ must be installed on the agent)

• Mercurial (the Mercurial "hg" client v1.5.2+ must be installed on the TeamCity agent machine)

• Team Foundation Server 2005, 2008, 2010, 2012, and (since TeamCity 8.0.6) 2013 (requires Team Explorer to be installed on the build agent, available only on Windows platforms)

• Perforce (a Perforce client must be installed on the TeamCity agent machine)

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

Labeling Build Sources

• Subversion

• CVS

• Git

• Mercurial

• Team Foundation Server

• Perforce

• Borland StarTeam

• ClearCase

• SourceGear Vault

Remote Run on Branch

• Git

• Mercurial

Feature Branches

• Git

• Mercurial

VCS Systems Supported via Third Party Plugins

• AccuRev

• Bazaar

• PlasticSCM

Issue Tracker Integration

• JetBrains YouTrack 1.0 and later (tested with the latest version).

• Atlassian Jira 4.4 and later (all major features also reportedly worked for version 4.2).

• Bugzilla 3.0 and later (tested with 3.4). 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 Plugin: Eclipse versions 3.4.2-3.8 and 4.2-4.3 are supported. Eclipse must be run under JDK 1.5+

• IntelliJ Platform plugin: compatible with IntelliJ IDEA 9.x - 13.x and (since 8.1.5) 14 (Ultimate and Community editions) and other IDEs based on the same version of the platform, including JetBrains RubyMine 2.0+, JetBrains PyCharm 1.0+, JetBrains PhpStorm/WebStorm 1.0+, AppCode 1.0+

• Visual Studio Addin 2005, 2008, 2010, 2012, and (since TeamCity 8.0.6) 2013. Installed .NET Framework is required.

Remote Run and Pre-tested Commit

Remote run and Pre-Tested (Delayed) Commit functionality is available for the following IDEs and version control systems:

Code Coverage

Supported Databases

See more at Setting up an External Database

• HSQLDB 1.8/2.x (internal, used by default) 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+ (Please 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, 2008 and 2012 (including Express editions); SSL connections support might require these updates.

• PostgreSQL 8+

• Oracle 10g+ (TeamCity is tested with driver version 10.2.0.1.0)