TeamCity: user’s experience and new features

It is always a pleasure to get a positive feedback on the products we develop, especially enterily new ones. We really appreciate the Continuous Integration Revisited post, where the author describes TeamCity’s features and his own experience. He noted that TeamCity’s installation and configuration was really quick and transparent, pointed at the benefits of the Delayed commit feature, and discussed possibility of creating the build configurations using different build runners and testing frameworks for remote code testing.
Now about new features that are not mentioned in this review, since they appeared only in the latest EAP build (that you can download at http://www.jetbrains.net/confluence/display/TW/Download). Among several enhancements and new features, the most important one is displaying of the Code Inspection results in a dedicated tab on Results page. Now you can locate the dead code, find probable bugs, check coding guidelines and specifications violations right on the web. TeamCity’s code inspections are based on the IntelliJ IDEA’s Static Code Analysis and Code Inspection tool, so you can use the power of more than 600 code inspections for remote code analysis.

Right now, you can’t navigate to the discovered problems from the web to IntelliJ IDEA. But this functionality will be implemented in the nearest IntelliJ IDEA EAP builds.

To get the full list of changes and new features in TeamCity EAPs, monitor the changes log.

Technorati tags: continuous integration, IntelliJ, IDE, Java, .NET, code coverage, code inspection, TeamCity
image description