Supported Platforms and Environments

Platforms (Operating Systems)



The TeamCity Server



The TeamCity server is web application that should be deployed into capable J2EE servlet container. Core functions of TeamCity server are platform independent.

Requirements:

• Java (JRE) 1.5+ (already included in Windows .exe distribution). TeamCity is tested with Sun JDK. Both 32bit and 64bit JDK versions can be used, but 32bit is Installing and Configuring the TeamCity server.

• J2EE Servlet (2.4+) container, JSP 2.0+ container based on Apache Jasper. TeamCity is tested under Tomcat 6 which is a recommended server. Tomcat 6 is already included in Windows .exe and .tar.gz distributions. TeamCity is reported to work with Jetty and Tomcat 5.

  note

  Please note that Tomcat version 5.5.20 is not compatible with TeamCity because this version of Tomcat contains a number of bugs.

TeamCity server is tested under the following operating systems:

• Linux

• MacOS X

• Windows XP

• Windows Vista/Windows Vista 64

• Windows 7/7x64 under Tomcat 6 web application server.

Reportedly works on:

• Solaris 10

• FreeBSD 7

Build Agents



TeamCity Agent is a standalone Java application.

Requirements:

• Java (JRE) 1.5+ (already included in Windows .exe distribution; JDK (JRE is not enough) is necessary for IPR, Java Inspections and Duplicate Finder runners)

TeamCity agent is tested under the following operating systems:

• Linux

• MacOS X

• Windows 2000/XP/XP x64/Vista/Vista x64

• Windows 7/7x64

Stop build functionality



Build stopping is supported on:

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

• Linux on x86, x64, PPC and PPC64 processors

• Mac OS X on Intel and PPC processors

• Solaris 10 on x86, x64 processors

The Windows Tray Notifier



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

Web Browsers



The TeamCity Web Interface is W3C complaint code, so just about any browser should work well with TeamCity. The following browsers have been specifically tested and reported to work correctly:

• Microsoft Internet Explorer 6, 7 and 8

• Mozilla Firefox 2, 3, 3.5, 3.6

• Opera 9.5, 10.0

• Safari 3+ under Mac/Windows

• Google Chrome

Build Runners



TeamCity provides a very wide of build tools support enabling both Java and .Net software teams building their projects.

Supported Java build runners:

• Ant 1.6-1.8 (TeamCity comes bundled with Ant 1.7.1)

• Maven2 versions 2.0.x, 2.x (TeamCity comes bundled with Maven 2.2.0)

• IntelliJ IDEA 5, 6, 7, 8, 9 projects

• JDK 1.5+ set in JAVA_HOME environment variable for the following runners: IPR, Java Inspections, Java Duplicates.

Supported .Net platform build runners:

• MSBuild (requires .Net Framework or Mono installed on the build agent)

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

• Microsoft Visual Studio Solutions (2003, 2005, 2008, 2010) (requires correspondent MS Visual Studio installed on the build agent)

• FxCop (requires FxCop installed on the build agent)

• Duplicates Finder for Visual Studio 2003, 2005, 2008 and 2010 projects. Supported languages are C# up to version 4.0 and Visual Basic .Net version 8.0 - 10.0 (requires .Net Framework 2.0+ installed on the build agent)

• Command Line Runner for running any build process by a command line

Testing Frameworks



• JUnit 3.8.1+, 4.x

• NUnit 2.2.10, 2.4.x, 2.5.x

• TestNG 5.3+

• MSTest (requires appropriate Microsoft Visual Studio edition installed on build agent)

Version Control Systems



• Borland StarTeam 6 and up (StarTeam client application should be installed on TeamCity server)

• CVS

• IBM Rational ClearCase, Base and UCM modes (ClearCase client should be installed on TeamCity server)

• Microsoft Visual SourceSafe 6 and 2005 (SourceSafe client should be installed on TeamCity server, available only on Windows platforms)

• Perforce (Perforce client should be installed on TeamCity server)

• Subversion

• Team Foundation Server 2005, 2008 and 2010 (Team Explorer should be installed on TeamCity server, available only on Windows platforms)

• Git

• Mercurial (Mercurial "hg" client should be installed on the server)

• SourceGear Vault (Command line client libraries must be installed on the server)

Checkout on agent



These are additional requirements if you need to use "checkout on agent" mode.

• CVS

• Subversion

• Team Foundation Server 2005, 2008 and 2010 (requires Team Explorer to be installed on the build agent)

• Mercurial (Mercurial "hg" client should be installed on the build agent)

• Git (since TeamCity 5.1.1)

Labeling Build Sources



• Borland StarTeam

• ClearCase

• CVS

• Perforce

• Subversion

• Mercurial

• Git

• Team Foundation Server

VCS Supported Via Separate Download Plugins



• AccuRev by third party

Issue Tracker Integration



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

• Atlassian Jira 3.10 and later.

• Bugzilla 3.0 and later (tested with 3.4). See additional requirements on 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:

• Eclipse 3.2-3.6, running under JDK 1.5+

• IntelliJ Platform plugin: compatible with IntelliJ IDEA 7.x, 8.x, IntelliJ IDEA 9.0.x (Ultimate and Community editions); JetBrains RubyMine 2.0

• Microsoft Visual Studio 2005, 2008 and 2010

Remote run and Pre-tested commit functionality is available for the following IDEs and version control systems:

External Databases



See more at Setting up an External Database

• HSQLDB

• MySQL 5.0.33+ (Please note that due to bugs in MySQL at least versions 5.0.20 and 5.0.22 are not compatible with TeamCity)

• Microsoft SQL Server 2005, 2008

• PostgreSQL 8+

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