TeamCity On-Premises 2023.11 Help

Supported Platforms and Environments

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

Operating Systems

TeamCity Server

TeamCity Server is a web application that runs within a capable J2EE servlet container. It requires a Java SE JRE installation to run. See notes on how to install Java on a TeamCity server.

Supported Java Versions

Supported Java versions: OpenJDK and Oracle Java 8 (8u16 or later) to 17 (32 or 64 bit). Using 64-bit Java is recommended.

The TeamCity server Windows installer and server Docker images come bundled with Amazon Corretto 64-bit Java 17.

For Apple ARM systems (for example, Apple M1 or M2), consider using a different version of Java, like Azul OpenJDK.

Supported Platforms

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

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, 2022

  • Server Core installation of Windows Server 2016

  • Windows 10 and 11 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

Windows XP/XP x64 are not supported.

Regarding architectural compatibility, TeamCity is not limited to any specific list. The verified and thoroughly tested architectures include:

  • Intel x86

  • AMD64 (x86_64)

  • Apple Silicon (M chips)

  • Amazon ARM (Graviton)

If you are using a different architecture that is not explicitly mentioned above, you may expect the TeamCity server to support it, provided that your operating system is supported and a suitable Java Virtual Machine (JVM) option exists.

TeamCity Agent

TeamCity Agent is a standalone Java application. It requires a Java SE JRE installation to run. See notes on how to configure Java on agents.

Supported Java Versions

Supported Java versions: OpenJDK and Oracle Java 8 (8u16 or later) to 17 (32 or 64 bit). Using 64-bit Java is recommended.

The TeamCity agent Windows installer and agent Docker images come bundled with Amazon Corretto 64-bit Java 17.

For Apple ARM systems (for example, Apple M1 or M2), consider using a different version of Java 17, like Azul OpenJDK.

Supported Platforms

TeamCity Agent is tested under the following operating systems:

  • Linux

  • macOS

  • Windows 7/7x64

  • Windows 10

  • Windows Server 2003/2008, 2012, 2016, 2019, 2022

  • 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

Regarding architectural compatibility, TeamCity is not limited to any specific list. The verified and thoroughly tested architectures include:

  • Intel x86

  • AMD64 (x86_64)

  • Apple Silicon (M chips)

  • Amazon ARM (Graviton)

If you are using a different architecture that is not explicitly mentioned above, you may expect the TeamCity Agent to run on it, provided that your operating system is supported and a suitable Java Virtual Machine (JVM) option exists.

Browsers

The TeamCity web interface is mostly W3C-compliant, so any modern browser should work well with TeamCity. The recent versions of the following browsers have been specifically tested and reported to work correctly:

  • Google Chrome

  • Mozilla Firefox

  • Safari under macOS

  • Microsoft Edge

  • Opera

Build Runners

Java Runners

Runner

Supported versions

Bundled versions

Ant

1.6-1.10

1.10.10

Maven

2.0.x, 2.x, 3.x

2.2.1, 3.0.5, 3.1.1, 3.2.5, 3.3.9, 3.5.4, 3.6.3, 3.8.6

IntelliJ IDEA Project

Gradle

0.9-rc-1 or later

Java Inspections

Java Duplicates

.NET Runners

We recommend that you use the unified .NET runner to run .NET projects in TeamCity. See its requirements here.

Other .NET runners:

Runner

Supported versions

Requirements

C# Script

.NET 6.0 or later

.NET 6.0 or later installed on the build agent, or can be run inside a Docker container with .NET 6.0 or later

MSBuild

Microsoft Build Tools 2013, 2015, 2017, 2019

.NET Framework or Mono installed on the build agent

NAnt

0.85 - 0.91 alpha 2

.NET Framework or Mono installed on the build agent

Microsoft Visual Studio Solutions

A corresponding version of Microsoft Visual Studio installed on the build agent

FxCop

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

.NET Framework 4.6.1 or later installed on the build agent

Inspections for .NET based on ReSharper Command Line Tools

.NET Framework 4.6.1 or later installed on the build agent

.NET Process Runner

.NET installed on the build agent

NuGet

NuGet 1.4 or later

Required on the build agent:

  • NuGet.exe command-line tool

  • on Windows: NuGet versions prior to 2.8.6 — .NET Framework 4.0 or later; NuGet 2.8.6 or later — .NET Framework 4.5

  • on Linux and macOS: Mono 4.4.2 or later and NuGet CLI 3.2 or later

Other Runners

Runner

Supported versions

Requirements

Command Line

Python

2.0 or later

Python installed on the build agent

Kotlin Script

Node.js

Rake

0.7.3 gem or later

PowerShell

1.0 - 5.0

Xcode

3-13

Xcode installed on the build agent

Testing Frameworks

Framework

Supported versions

Requirements

JUnit

3.8.1+, 4.x

NUnit

2.2.10, 2.4.x, 2.5.x, 2.6.x, 3.0.x

TestNG

5.3 or later

MSTest and VSTest

8.x-12.x, 14.x, 15.x, 19.x are supported by the .NET runner

A corresponding Microsoft Visual Studio edition or Visual Studio Test Agent installed on the build agent

MSpec

MSpec installed on the build agent

Read more about the support for testing frameworks in TeamCity.

Version Control Systems

VCS Support on Server

VCS

Supported versions

Requirements

Git

For automatic git gc support and maintenance of Git clones, requires a Git client installed on the server

Subversion

Server versions 1.4-1.9 or later

Perforce

A Perforce Helix Core client installed on the server (2017.1+ versions are supported).

Azure DevOps

2005, 2008, 2010, 2012, 2013, 2015, 2017

Mercurial

A Mercurial "hg" client v1.5.2+ installed on the server

CVS (via an external plugin)

Borland StarTeam

6 or later

A StarTeam client application installed on the server

Other VCSs can be supported in TeamCity via external plugins.

VCS Support on Agent

VCS

Supported versions

Requirements

Git

1.6.4 or later

A Git client installed on the agent

Subversion

1.4-1.8

Perforce

A Perforce client installed on the agent

Azure DevOps

2005-2015, 2017

Mercurial

A Mercurial "hg" client v1.5.2+ installed on the agent

CVS

Labeling Build Sources

  • Git

  • Subversion

  • Perforce

  • Azure DevOps

  • Mercurial

  • CVS

  • Borland StarTeam

Remote Run

  • Git

  • Mercurial

Feature Branches

  • Git

  • Mercurial

VCS Hosting Services

Cloud Platforms

The following cloud platforms can be used to run build agents:

Available as non-bundled plugins:

Issue Trackers

Tracker

Supported versions

JetBrains YouTrack

1.0 or later

Atlassian Jira

4.4 or later (all major features also reportedly worked for version 4.2)

Bugzilla

3.0 or later

GitHub

0.9-rc-1 or later

Bitbucket Cloud

Azure DevOps Server (formerly Team Foundation Server — supported version 2012 or later), and Azure DevOps Services

See also additional requirements.

IDE Integration

TeamCity provides productivity plugins for the following IDEs:

IDE

Supported versions

Requirements

IntelliJ Platform Plugin

Compatible with IntelliJ IDEA 2019.3 - 2021.2.3 (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, 2019

.NET Framework

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

IntelliJ IDEA Platform

(supported only for VCS integrations bundled with JetBrains IDEs)

  • Subversion

  • Perforce

  • Git (remote run only)

  • Azure DevOps, or formerly Team Foundation Server

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 (formerly Team Foundation Server — supported version 2005 or later). Installed Team Explorer is required.

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

Code Coverage

IDE

Supported Coverage Tools

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.

Databases

Database

Supported versions

HSQLDB(The internal HSQLDB database can be used for __evaluation purposes only__.)

2.3.2

MySQL

5.7.34 or later

Microsoft SQL Server

2012 or later (including Express editions), SQL Azure

PostgreSQL

9.6 or later

Oracle

10g or later (tested with the [driver](https://www.oracle.com/technetwork/database/features/jdbc/index-091264.html) version 12.1.0.1

MariaDB

10.2 or later

Read more details.

Game Engines

  • Unity, by the means of the Unity Support plugin (bundled in TeamCity Cloud and can be installed on-demand in TeamCity On-Premises)

Last modified: 04 March 2024