Do you take continuous integration seriously? Do you want to have a stable trunk and green builds? If so, TeamCity will provide numerous features to support you all the way.
Remote Run and Pre-Tested Commit
With TeamCity you can build, check and run automated tests on the server even before committing your changes — keeping your code base clean at all times.
These features are provided via IDE plugins for IntelliJ IDEA-based products, Microsoft Visual Studio and Eclipse.
Problem and Test Management
Several persons can be assigned for investigation of problems in one build. For example, Jane researches why the process exited with code 1, while Bill fixes some tests.
When a problem is assigned, notification(s) are sent to the corresponding person(s).
On-the-fly build progress reporting
TeamCity tracks different stages of the build and reports all the information on the fly - both in the web UI and in all supported IDEs. You don’t have to wait for a build to finish to discover that something is wrong.
TeamCity alerts you about failed tests immediately and provides details on encountered errors.
Newly Failed Tests and "Fixed in"
When newly checked-in code fails a test, TeamCity immediately shows it. If a test did not fail in the previous build, it will be shown as a "New" failed test.
For a failed test, you can see the build in which it failed for the first time and what changed in this build.
Risk Group tests reordering
For certain build tools like Ant, Gradle, MSBuild and some others, you can configure TeamCity to change order of tests.
For example, recently failed or new tests can be started before others to provide even faster feedback to the developer.
TeamCity offers multiple ways to instantly notify you about build problems or any other changes in your projects.
Be notified by email, instant messenger, or get notification right in your IDE.
You can set up multiple notification rules on all kinds of events, and also choose the order in which they are processed.