New in 3.1
Statistics Improvements
Build Agents' Workload Statistics
More visual metrics, namely, statistics of Build Agents' activity and their usage during a particular time period are now available.
We are sure you'll find this feature helpful in:
- your daily administration activities for lowering your company's network workload
- finding and eliminating the gap between the most frequently used computers and those which are often idle
- reducing the cost of your hardware resources ownership
"Time to fix tests" Statistics
A new type of statistical data display: time it took to fix the build's tests.
Publishing Build Artifacts while the Build is Still Running
Now you can notify TeamCity as soon as the build artifacts are created so they can be uploaded and available even before the build is finished. It increases your builds responsiveness and you don't need to wait until your builds are finished.
Notifications Improvements
Receive notifications only when the build status changes
When watching builds of the specific build configurations, you can opt to receive notifications:
- on the first failed build after successful
- on the first successful build after failed
Ability to watch all projects
When customizing the notification rules, besides the Watch builds of the selected build configurations you can now select All projects to monitor all builds of all the projects' build configurations.
User Interface Enhancements
Viewing and navigating to any build configuration
From any place in TeamCity user interface you can now navigate to any build configuration by just pressing the arrow button in the Projects tab and selecting the desired build configuration
Viewing the queued builds information on the Projects page
View the queued builds' information along with their start and finish estimates and reorder the queue without switching to the Build Queue page.
Duplicates and Inspections viewers enhancements
An improved viewer for browsing the discovered code duplicates and inspections allowing to filter the results by directories. The Duplicates Viewer now provides syntax highlighting.
New Search Possibilities
Search for builds run on a Build Agent and filter history by Agent name
In addition to searching by build number, project or a build configuration name, you can now search by the Build Agent the build was run on, and it's also possible to search for the builds created on a particular Build Agent on the build configuration History page.
Tests filtering
It's now possible to filter the build tests list by the test or package name:
Improved Builds Clean-Up Policy
You now have a more fine-grained control on a data to be cleaned up. Choose between keeping only the statistical data and build history without artifacts.
.NET Testing Framework Support Enhancements
- In addition to NAnt version 0.85 now TeamCity supports NAnt 0.86 Beta 1
- Added ability to specify the mode (x86 or x64) to run the NUnit tests
- In addition to NUnit version 2.2.x now TeamCity supports NUnit 2.4.x
- Added support of NUnit tests categories for NAnt, MSBuild, solution 2005 and 2008 build runners, and NUnit Launcher
Custom Tests Reporting
You can now benefit from TeamCity's tests reporting possibilities even when your testing framework is not directly supported by TeamCity. By printing the specially formatted messages to the build standard output, you send test events to TeamCity and get on-the-fly test reporting. This feature can be useful for custom frameworks support and doesn't require developing a fully-fledged TeamCity plugin.
Miscellaneous
TeamCity Enterprise Version Enhancements:
- Windows Domain Authentication under Linux is now supported.
- Cron Build Trigger - Now you can use Cron Expressions for triggering your builds.
- Improved external database support - Now TeamCity supports Oracle as an external database, and the database migration tool provides migration in any direction.
- Parallel tests running support - TeamCity now correctly reports JUnit and TestNG tests run in parallel via Ant "parallel" task or TestNG paralleling.
- Possibility to type a comment in the Take responsibility dialog in Eclipse plugin
- StarTeam support improvements
- Guests in TeamCity Professional edition now do not have access to the Build Agent details page. The same is true for the "Project Viewer" role in Enterprise edition.
New in 3.0
Per-project Access Rights
Different types of user roles (only available in Enterprise edition) allow you to configure the level of access to the TeamCity feature set according to your company's needs.
TeamCity Professional provides a fixed set of roles for all projects (guests, users, and system administrators). The Enterprise edition provides more flexibility: you can assign one or several roles for users in the same project, and users will have different types of permissions, for example, only to monitor project status, or to manage projects and build agent configurations, or handle standard software developer's tasks: run and stop builds, reorder the build queue, take responsibility, pin and tag builds, and more.
Build Statistics Charts
TeamCity regularly collects data about build results and provides a set of visual reports to help you monitor your projects' health:
- the frequency and success rate of your builds over time
- build durations
- time that builds spend in the build queue
- trends on the number of tests
- trends on the size of artifacts
- the number of discovered issues when inspecting code
- code duplicates and code coverage trends
A number of handy filters help examine data from different perspectives, for example, view average values, exclude info on failed builds, and filter out info based on the date.
As with many other TeamCity features, the statistics display is also customisable, and you can easily add your own graphs.
VCS Integration Improvements
We have implemented full-featured support for another industry-wide version control system, StarTeam, which you can now use when setting up VCS roots for your projects. You can also perform pre-tested commits from IntelliJ IDEA to your StarTeam repository.
You can now add labels for your finished builds with CVS, Subversion, Perforce, StarTeam, or ClearCase VCS roots. Apply the VCS labels to all builds or only to successful ones; you can also label build sources manually (available for finished builds).
To simplify administering TeamCity projects and configuring VCS roots, it is now possible to share identical repository roots across different projects. When you modify shared VCS root settings, TeamCity always monitors whether your changes might somehow affect more than one project and warns you about that possibility.
Improved Quality Maintenance
A long-awaited feature for .NET platform developers has now arrived: with the .NET Duplicates Finder, you can now catch similar fragments of your C# and Visual Basic .NET code in Visual Studio 2003, 2005 and 2008 solutions. Whenever duplicate blocks of code are discovered, they are shown in a convenient report. TeamCity 3.0 supports C# up to version 2.0 and covers Visual Basic .NET up to version 8.0.
Formerly available only for IntelliJ IDEA projects, Code Inspections and Duplicates Analysis now work for Maven2 projects as well.
In addition to the existing support for pre-tested commit into the Team Foundation Server project repository, you can use this feature if your project code base is under Subversion control.
Miscellaneous
A brand-new troubleshooting feature - a thread dump of a running build - provides a view of the build process tree to easily identify the source of problems in the build.
TeamCity assists you with build process troubleshooting: it determines builds which, for some reason, may be hanging. To be aware of this kind of situation, you can select to receive corresponding notifications.
The Build Queue now provides more detailed information on the status of pending builds, in particular:
- the expected build start time
- the expected build finish time with the estimated build duration available as a tooltip
- the build agent where TeamCity plans to run a build
- how the build was triggered
- a list of build agents that can run the build (additionally the current agent status is available in a pop-up window)
This information makes it easier to manage and monitor the process of creating builds in TeamCity's build grid.
With build tags available in TeamCity 3.0, you can:
- organise the history of your builds
- quickly navigate to the builds marked with a specific tag
- search for a build with a particular tag
Assign any number of tags to a single build depending on your needs.
Find builds by their number, tag, or build configuration name. You can use multiple keywords to narrow your results.
RSS Feeds
- To stay on top of things you can now get reports on the status of builds via syndication feeds. You can specify the content of your personalised RSS feed by selecting from a wide range of settings and subscribe to it, for example, using an external application. The feed entries summarise build results and contain links to the build changes and the build log.
UI Improvements
- We have made numerous improvements to the Build Results, Build Configuration, and My Changes pages.
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.
Supported Java build runners:
- 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 use Command Line for building your projects using any script.
Version Control Systems
TeamCity supports industry-wide version control systems including:
- Subversion
- Perforce
- CVS
- Borland StarTeam
- Microsoft Visual SourceSafe
- Team Foundation Server 2005
- Team Foundation Server 2008
- IBM Rational ClearCase (Base and UCM)
Supported IDEs
TeamCity integrates with industry-leading IDE's - IntelliJ IDEA, Eclipse, and Microsoft Visual Studio - allowing both Java and .NET developers to get rapid feedback on the integration of their changes.
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,
- analyse 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 your 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 visualise 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
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
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.
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 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