TeamCity 4.0 Help

Supported Platforms and Environments

Platforms (Operating Systems)

The TeamCity Server

The TeamCity server is platform independent.

Requirements:

  • Java (JRE) 1.5+ (already included in Windows .exe distribution). TeamCity is tested with Sun JDK.

  • J2EE Servlet (2.4+) container, JSP 2.0+ container. 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.

TeamCity server is tested under the following operating systems:

  • Linux

  • MacOS X

  • Windows XP

  • Windows Vista/Windows Vista 64 under Tomcat 6 web application server.

Reportedly works on:

  • Solaris 10

  • FreeBSD 7

Code Fragments Syntax Highlighting

The syntax highlighting (in the web difference view and Duplicates results) is available only under:

  • Windows 32 bit platforms (workaround is Known Issues for Windows 64)

  • Linux 32 bit platforms Under other platforms the views will function normally, but the syntax highlighting will not be available.

Build Agents

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

Stop build functionality

Build stopping is supported on:

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

  • 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

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 and 7

  • Mozilla Firefox 2 and 3

  • Opera 9.5

  • Safari 3 under Mac

  • 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.7 (TeamCity comes bundled with Ant 1.7.0, since TeamCIty 4.5 - with Ant 1.7.1)

  • Maven2 2.0.x (TeamCity comes bundled with Maven 2.0.9, since TeamCity 4.5 - with Maven 2.0.10)

  • IntelliJ IDEA 5, 6, 7, 8 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 (since TeamCity 4.5) Mono installed on the build agent)

  • NAnt versions 0.85 - 0.86 (requires .Net Framework or (since TeamCity 4.5) Mono installed on the build agent)

  • Microsoft Visual Studio Solutions (2003, 2005, and 2008) (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 and 2008 projects. Supported languages are C# up to version 2.0 and Visual Basic .Net up to version 8.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

  • TestNG 5.3+

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

Version Control Systems

Checkout on server

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

  • CVS (client is bundled)

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

  • Microsoft Visual SourceSafe 6 and 2005 (SourceSafe client should be installed on TeamCity server to use VSS integration)

  • Perforce (Perforce client should be installed on TeamCity server to use Perforce integration)

  • Subversion (client is bundled)

  • Team Foundation Server 2005 and 2008 (Team Explorer 2005 or 2008 should be installed on TeamCity server to use TFS integration)

Checkout on agent

  • CVS

  • Subversion

  • (since TeamCity 4.5) Team Foundation Server 2005 and 2008 (requires Team Explorer 2005 or 2008 installed on the build agent)

Labeling Build Sources

  • Borland StarTeam

  • ClearCase

  • CVS

  • Perforce

  • Subversion

VCS Supported Via Separate Download Plugins

  • Mercurial by JetBrains, beta quality

  • AccuRev by third party, alpha quality

IDE integration

TeamCity provides productivity plugins for the following IDEs:

  • Eclipse 3.2, 3.3, 3.4, running under JDK 1.5+

  • IntelliJ IDEA 7.0, and 8.0

  • Microsoft Visual Studio 2005, and 2008

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.5 integration plugins. Subversion 1.6 is supported since TeamCity 4.5.2

  • Perforce 2008.1 (2008.2 is supported since TeamCity 4.5)

  • since TeamCity 4.5 CVS Eclipse Plugin

IntelliJ IDEA

  • ClearCase

  • CVS

  • Perforce

  • StarTeam

  • Subversion

  • Visual SourceSafe

MS Visual Studio

  • Subversion

  • Team Foundation Server

  • since TeamCity 4.5 (EAP build 8804) Perforce)

External Databases

  • 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

  • PostgreSQL 8+

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

Last modified: 20 April 2023