This is the first EAP of the TeamCity 5.0 (code name Darjeeling).
Issue Tracker integration
Issues are now first class citizens in TeamCity. Out of the box TeamCity integrates with Jira, Bugzilla and Jetbrains own tracker Charisma. Plugins can be written to support other trackers. There is also Open API for working with issues.
Issue tracker integration is configured on a separate tab of the Server configuration page:
After that TeamCity will start recognizing issue ids mentioned in the change or build comments and associates issues with builds. You can see change details by moving your mouse over issue id:
If build contains changes with issues mentioned in them, then new tab will appear where build related issues are shown:
Note that the issue is considered resolved in a build if the build includes the last change, in which this issue is mentioned.
There is also Issue Log page made similar to Changes Log. It shows issues detected by TeamCity optionally grouped by builds:
Java and .NET Coverage
Coverage support was significantly improved in TeamCity 5.0 for both Java and .NET.
For Java TeamCity supports new coverage engine: IntelliJ IDEA built-in coverage. Read more about it here.
For .NET starting with TeamCity 5.0 supports NCover and PartCover coverage engines and you no longer need to integrated coverage manually.
Single change status page
Status of the change across all build configurations where it was attached and build can now be seen on a single page:
Various actions are now stored in the Audit log which can be browsed from the web UI:
You can now browse server logs right from the web UI and download the whole zip of the logs.
Administration UI for artifact-based (report) tabs
In previous versions of TeamCity artifact-based tabs can only be configured by editing configuration files manually. Now there is convenient UI for these tasks:
You can now easily archive no longer active projects. Archived projects will be shown on the separate tab in the Administration area, their build configurations will be paused and changes collecting for their VCS roots will be stopped (if VCS roots are not shared with active projects). Builds however can be triggered manually, and project/build configuration settings can be edited.