One of TeamCity's remarkable features is a possibility to analyze the code of your application, find duplicates, show corresponding reports and charts. You can calculate code coverage metrics, run code inspections, and see results right in the TeamCity's UI. And in most cases, these features work out of the box, without setting up additional external plugins. All these code examining tools generate various numeric metrics, and you can see the dynamic of their change in the TeamCity UI. What you could not do before (well, almost could not) is to specify metric thresholds, which would fail th

In the upcoming TeamCity 5.1 we've added an often requested feature - artifact packaging. As you probably already know, in TeamCity you can easily configure artifact upload to the server. Later, from a build page, you can download all artifacts of the build. You can specify both directories and individual files as artifacts. The syntax for this is rather simple. Build artifacts enable another really popular feature - custom reports. The essence of the feature is that if your build produces a report, viewable in a browser (any HTML/Text/Image/PDF), you can integrate this build report into

In fact, this feature existed since TeamCity 1.0, though it isn't much publicized. Yes, we admit that we are lazy developers, and we don't like to restart the programs after editing their configuration files. That's why IntelliJ IDEA monitors the changes on the disk and reloads files automatically after an external change takes place. And the same is true about TeamCity: it monitors the state of the configuration files and picks up the changes if the files were modified. FYI: TeamCity server uses XML-based configuration files to store information about system-wide settings, such as authentic

Hello, We are glad to announce the first EAP build of TeamCity 3.0 (codename Benares). It has significant number of new features as well as fixes, usability and performance improvements. It is pretty stable - we run TeamCity EAP as an internal JetBrains build server which serves dozens of projects of various types (.NET, Java) in multiplatform environment (MacOS, Windows, Linux). Most noticeable features of this build include: Per build configuration, shareable VCS Roots Visual Studio pre-tested commit support for Subversion StarTeam support Build queue now features estimated build sta

Hello everyone, It is the time to reveal some plans regarding the next version of TeamCity. First of all, as long as code-names for TeamCity are city names, we've chosen Benares name for this version. Benares will be released this year, and more specific dates are not settled yet. The most optimistic date for the release is November, 1 After a lot of disputes with development team, marketing and our customers (mostly represented by Jira votes) we've prepared a first version of roadmap for the Benares. One of the key ideas for TeamCity future is to go beyond continuous integration and bui

The 2.0 release of TeamCity was packed with features. But appetite comes with eating, and the more features we offer to our users the more requests for improvements and enhancements we get with every new release. Well, at least this keeps us going in the right direction ;) The 2.1 version of TeamCity we release today lists a fair number of various improvements to existing features, plus several new features you might enjoy: More stable and complete integration with Subversion and ClearCase Ipr, Inspection and Duplicates finder runners related fixes Ivy-related improvements, including p

Hello everyone, We are going to release a minor update to TeamCity 2.0 in May, which will include several new features and a critical bugfixes. So today the first EAP build for this version of TeamCity is published. My favorite feature in this EAP is "Run on agent", when you can schedule a build on the specific agent: You can read release notes for this build, view Jira changelog and download the software. You're welcome to participate in our EAP program to provide feedback on its features, and you can get help working with TeamCity in our discussion forum. With kind regards, Kirill Max