TeamCity Cloud 2020.2 Help

Supported Platforms and Environments

Platforms (Operating Systems)

Build Agents

The TeamCity Agent is a standalone Java application. TeamCity Cloud supports two types of agents:

  • Hosted by JetBrains

  • Hosted by a customer

You can combine agents of both types in your installation. Read more information on licensing these agents in Subscription and Licensing.

JetBrains-Hosted Agents

These agents are automatically maintained by JetBrains and don't require to be installed or configured by a customer. There are multiple types of these agents:

Instance Type

Hardware

Linux (small)

  • CPU: 2 vCPU (Intel Xeon (Cascade Lake))

  • RAM: 4 Gb ram

  • SSD: 20 Gb

Linux (medium)

  • CPU: 4 vCPU (Intel Xeon (Cascade Lake))

  • RAM: 8 Gb ram

  • SSD: 20 Gb

Windows (medium)

  • CPU: 4 vCPU (Intel Xeon (Cascade Lake))

  • RAM: 8 Gb ram

  • SSD: 20 Gb

Each JetBrains-hosted agent comes with a set of preinstalled software.

Software preinstalled on Windows agents:

SoftwareVersion
Unity2020.2.3
JDK11.0.10_9, 8.272.10.3, 15.0.2.7.1
.NET
Git2.30.1
kubectl1.20.4
AWS CLI2.1.26
WiX Toolset3.11.2
NUnit3.12.0
Z-Zip19.0
Yarn1.22.5
Docker19.03.14
Docker Compose1.28.2
Gradle6.8.2
CMake3.19.4
Ruby3.0.0.1, 2.7.2.1, 2.6.5.1, 2.5.3.101
Ruby2 DevKit4.7.2.2013022403
RTools
Node.jsv14.16.1

Software preinstalled on Ubuntu agents:

SoftwareVersion
Git2.31.1
Git LFS2.13.3
Docker20.10.6
Docker CLI20.10.6
Docker Compose1.28.0
AWS CLI1.18.69
kubectlv1.21.0
Android SDK6858069
Perforce
Mercurial5.3.1
SVN
Helmv3.5.0+g32c2223
Yarn
Ant1.10.7
Gradle6.8.1
CMakr3.19.5
PowerShell7.1.1
R3.6.3
Groovy3.0.7
RVM1.29.12-next
rustup1.23.1
Cargo1.51.0
rustc1.51.0
Go1.16
NVM0.33.11
Node.js14.5
Python3.8.5
Python22.7.18
Python33.9.4
pip321.0.1
pip21.0.1
Ansible2.9.6

Self-Hosted Agents

You can install a build agent locally on your machine, similarly to how you would do it in TeamCity On-Premises, and connect it to the TeamCity Cloud instance. Note that you need to acquire a concurrent build slot for each self-hosted agent.

Build agents require a Java SE JRE installation to run. See notes on how to configure Java on agents.

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

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

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

  • 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

For a unified .NET runner, see a dedicated section.

Other 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

Other runners

  • Python, requires installing Python version 2.0 or later on agents

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

  • PowerShell, versions 1.0 - 5.0

  • Xcode, versions 3-12 (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 .NET 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)

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)

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

Labeling Build Sources

  • Git

  • Subversion

  • Perforce

  • Team Foundation Server

  • Mercurial

Remote Run on Branch

  • Git

  • Mercurial

Feature Branches

  • Git

  • Mercurial

VCS Systems Supported via Third Party Plugins

VCS Hosting Services Integration

Issue Tracker Integration

Additional requirements are listed in Integrating TeamCity with Issue Tracker.

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, 2019 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)

  • 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

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

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: 28 April 2021