3.1

Server-side code analysis

• 600+ Java code inspections. The industry-richest set of unique code inspections allow to reach the highest level of code quality for Java projects (with .NET inspections coming soon).
• Search for code duplicates. A code quality feature, with configurable precision in code snippets comparison, allows you to consolidate your source code to the most optimized state.
• Code coverage analysis. The ability to check whether your project's code base is fully covered by tests. This feature encourages programming teams to adopt the test-driven development practice, which ensures that the code to be changed is covered by tests and can be safely modified.

Unique Pre-tested Commit Feature

• The Build Grid. This innovative approach allows running builds more frequently, and with more granularity, thanks to the intelligent distribution of build tasks among the available hardware resources. Builds can be run under different operating systems, environments and various configurations, all managed from a single place.
• An advanced and flexible notification system. Server notifications can be configured according to each developer's habits and/or needs and delivered via e-mail, instant messaging, the Windows Tray Notifier, RSS feeds, or even directly to an IDE UI.
• Taking Responsibility. Just a single click can save your teammates' time by immediately informing them when a particular build is being fixed by you.
• IDE integration. Developers are never distracted from coding, being able to handle builds, tests and reports directly in their IDE, be it IntelliJ IDEA, Eclipse or Microsoft Visual Studio.
• Web UI. The light-weight and convenient web interface allows the entire team to stay synchronized on the project status, as well as manage and monitor all its processes.

• Time-consuming operations performed on the server-side. Running tests, project-wide code analysis, etc are all done on the server, saving developers' local computing resources and time.
• Remote run of personal builds. Before making a decision on committing changes, any developer can configure and run personal builds on the server side, without the need to waste local hardware resources preventing further coding.
• Immediate reporting. If a test fails while the build is still running, the failure is immediately reported to the committer.
• Unique navigation capabilities. Links on the convenient web interface allow jumping from build/test results right to the originating code in the IDE editor.
• Integration with issue tracking systems. Ability to access an issue tracker via integration saves developers' time from switching back and forth between the two tools.

All of the features needed to successfully build, test and release professional software are tightly integrated in one environment. There is no need to search for separate tools, waste time on evaluating them and spend human resources on making them work together.

Intelligent integration of building, testing, versioning, analyzing and reporting tools in TeamCity, together with their compatibility with the most popular IDEs, allow anyone to adopt and start using all the features immediately, without breaking from any established processes.

As a result of the smooth adoption of supported practices and technologies and faster feedback cycles, the time for delivery of professional quality software is drastically cut, and the expenses related to further product maintenance are reduced.