Home> TeamCity> Features> Supported Platforms and Environments

Supported Platforms and Environments


Open the screenshot in a new browser window

Open the screenshot in a new browser window

TeamCity supports both Java and .NET software development teams and integrates with the most popular VCSs, IDEs and development frameworks to ensure a smooth and stable development workflow.



Build Runners

Supported Java build runners:

Open the screenshot in a new browser window

Open the screenshot in a new browser window

  • Ant
  • Maven2
  • IntelliJ IDEA projects
  • Code Inspections (Java, HTML and CSS, JavaScript, EJB, JSP, JSF, Struts and more) for IntelliJ IDEA projects and Maven2 projects
  • Duplicates Finder for IntelliJ IDEA projects and Maven2 projects

Supported .NET platform build runners:

  • MSBuild
  • NAnt
  • Microsoft Visual Studio Solutions
    • 2003
    • 2005
    • 2008
  • Duplicates Finder for Visual Studio 2003, 2005 and 2008 projects (C# up to version 2.0 and Visual Basic .NET up to version 8.0)

Plus you can select the Command Line runner and use any script to build your projects.

Testing Frameworks

TeamCity integrates with JUnit, TestNG and NUnit testing frameworks ensuring the most effective testing of your software.

.NET Testing Framework Support Enhancements

  • Support for NAnt 0.86 Beta 1 testing framework
    Now TeamCity supports NAnt versions from 0.85 to 0.86 Beta 1.
  • NUnit 2.4 support
    Now TeamCity supports NUnit versions 2.2.x and 2.4.x.
  • Ability to specify the mode (x86 or x64) to run the NUnit tests
  • NUnit tests categories support for NAnt, MSBuild, and NUnit Launcher

Version Control Systems

TeamCity supports industry-wide version control systemsincluding:

Open the screenshot in a new browser window

Open the screenshot in a new browser window

  • Subversion
  • Perforce
  • CVS
  • Borland StarTeam
  • Microsoft Visual SourceSafe
  • Team Foundation Server 2005
  • Team Foundation Server 2008
  • IBM Rational ClearCase (Base and UCM)
  • StarTeam support improvements

Notification and Monitoring

With TeamCity it is simply impossible to miss any important events which might take place during the automated building process. A wide range of predefined notification rules and events allow you to avoid information overload, yet stay tuned to the development process and switch applications only when it is really necessary.

E-mail

Open the screenshot in a new browser window

Open the screenshot in a new browser window

If you are more accustomed to receiving e-mail notifications, you can receive notifications via e-mail. TeamCity provides you with e-mails containing extracts of build results in the message subject and clickable links in the message body to access more information on TeamCity's Build Results page.


Jabber/XMPP

You can get notifications via the IDEtalk plugin in IntelliJ IDEA or a stand-alone Jabber client.

RSS

Open the screenshot in a new browser window

Open the screenshot in a new browser window

You can stay on top of things with build status reports via syndication feeds. You can specify the content of your personalized RSS feed by selecting from a wide range of settings and subscribe to itusing an external application. The feed entries contain a summary of the build results and links to the build changes and the build log.

IDE

When working with IntelliJ IDEA you can opt to receive notification popups when different events occur, such as a build's failure or responsibility changes, or when the first error has occurred in a build.

Windows System Tray

If you work in the Windows environment, you might want to be notified on the status of selected projects via the Windows Tray Notifier.

As the status of the builds you have selected to monitor changes, the icon in your system tray changes correspondingly. With just one click you can access the Quick View window and get the picture of the projects you are monitoring. Clickable links navigate to the TeamCity's web interface.

Tray Notifier

Supported IDEs

TeamCity integrates with industry-leading IDEs - IntelliJ IDEA, Eclipse, and Microsoft Visual Studio - allowing both Java and .NET developers to get rapid feedback on the integration of their changes via:

  • personal builds
  • pre-tested commit

Plus:

  • monitor the status of the integration your changes
  • navigate to tests results, stack traces and files from TeamCity in your IDE
  • work with code duplicates and code inspection results (available in IntelliJ IDEA)

Personal Builds

To test how successful your changes are you can create personal builds in TeamCity using the Remote Run feature. The modified files are submitted to the server bypassing the VCS. TeamCity obtains the latest source files from the project code base, creates a build and reports on the results.

Pre-tested Commit

Using the "pre-tested" commit feature the project code base always stays clean. The developer's code modifications get integrated into the latest version of source files in the VCS, and the tests are run remotely:

  • If the tests fail, the code is not integrated, the developer can safely work on a fix, and the team's work is not interrupted
  • If the build is successful, the changes are committed to the VCS automatically.

Open in Tests, Stacktraces, and Files in the IDE

In several clicks from TeamCity's web UI you can navigate to:

  • the code that failed unit tests in your IDE
  • the files in your project base

IntelliJ IDEA Integration

Pre-tested commit to StarTeam and IBM Rational ClearCase (Base + UCM ) is now supported.

With TeamCity integration in IntelliJ IDEA you can:

  • perform remote run and pre-tested commit to CVS, Perforce and Subversion
  • review code duplicates,
  • analyze the results of remote code inspections,
  • monitor the status of projects and build configurations and the status of changes committed to the project code base,
  • view failed tests and build logs
  • take responsibility for breaking the build
  • apply quick-fixes to the results of remote code analysis: the problematic code can be highlighted in the editor and you can work with a complete report of the project inspection results in a toolwindow
  • download and view only the new inspection results that appeared since the last build was created
  • work with the results of server-side code duplicates search in the dedicated toolwindow
  • access server-side code coverage information and visualize the portions of code covered by unit tests. When showing code coverage is enabled, the project view of the IDE shows the percentage of classes and lines covered by unit tests.

Eclipse Integration

For a quick overview of the TeamCity plugin for Eclipse, please see the Live demo

TeamCity integration with Eclipse provides multiple features:

  • personal builds and pre-tested commit
  • the projects status in the Watched Projects view
  • explore changes introduced in the source code and comparing the local version with the latest version in the project repository
  • navigate from build logs opened in Eclipse to files referenced in build log
  • view failed tests of a particular build
  • navigate to TeamCity's web interface
  • Possibility to type a comment in the Take responsibility dialog in Eclipse plugin

Microsoft Visual Studio 2005 and 2008 Integration

You can perform remote runs and pre-tested commits to the project code base under Subversion or Microsoft Visual Studio 2008.

For a quick overview of the TeamCity plugin for Microsoft Visual Studio, please see the Live demo

With TeamCity integration in Microsoft Visual Studio you can:

  • remote run and pre-tested commit to MS Team Foundation Server and Subversion
  • view the real-time build logs in the IDE
  • view failed tests of a particular build, including navigation to the results of failed tests from TeamCity's web interface to Visual Studio editor

Web Browsers

Use your favorite web browser to access TeamCity's features:

  • Microsoft Internet Explorer 6.0 and 7.0
  • Mozilla Firefox 1.5.x and 2.0
  • Opera 8.5.x and 9.0
  • Safari 2.0.x