TeamCity Blog

For the past several weeks we have been working really hard to solve a number of issues after the 3.1 version was released, and voilà - a hot tasty little pie called TeamCity 3.1.1 is right here

The release is mainly targeted on improving the performance, has a number of bugfixes and adds better performance for StarTeam.

You can download the latest version at the official website. And don’t forget to back up your data before upgrading.

And some more good news today. Laurent Kempé, the editor, founder, and primary contributor of Tech Head Brothers, has just published an article on his successful experience of integrating TeamCity with NCover - a tool for measuring the code coverage for .NET platform development. An integration result is possibility to get an overview of the project code coverage in a dedicated Code Coverage Summary tab of the build configuration.

We wish you a happy building with TeamCity 3.1.1 and we are really glad to hear about the concrete TeamCity usage examples!

The JetBrains TeamCity team

Technorati tags: TeamCity, JetBrains, IntelliJ IDEA, Eclipse, NCover, StarTeam, continuous integration, build management, agile development, MS Visual Studio 2005, MS Visual Studio 2008

We are glad to announce the EAP of Rake plugin for TeamCity. The plugin implements support of fully functional build runner and provides on-the-fly test reporting for the Test::Unit and RSpec testing frameworks.

The plugin is open-source and written in Java, and, of course, everyone is welcome to contribute.

Take a look at the working demo of the Rake builds in TeamCity at our public demo server, TeamCity Rake Runner Demo project, for example, Radiant:Spec build configuration.

To download the plugin, navigate to Teamcity Rake Runner project on the Projects page, point to the Artifacts link and download the plugin archive.

Please note that the plugin is compatible with TeamCity 3.1 and higher (the 3.1.1 version is going to be released really soon). For additional information please refer to the plugin description page and on-line reference.

We wish you a happy building with Rake Build Runner and eagerly wait for your feedback!

Technorati tags: TeamCity, JetBrains, IntelliJ IDEA, Eclipse, Rake, continuous integration, build management, agile development, MS Visual Studio 2005, MS Visual Studio 2008

Here, at JetBrains, we use TeamCity for building all our projects and TeamCity itself and have multiple build configurations for quite different purposes to thoroughly test our tools. All in all - about 700! build per day, 170 build configurations for:

• estimating code quality by discovering code duplicates, bugs, performance issues, and dead code and measure the code coverage with unit tests
• scheduled builds (such as, for example, nightly ones)
• “stress” tests and many other cases

Aaron Jensen has recently praised TeamCity’s possibilities, and now he shares real life examples of TeamCity’s build configurations set up in his company.

First and foremost, come the continuous integration builds triggered by VCS check-in and scheduled nightly builds.

He also uses TeamCity’s ability to specify the dependencies between the results of the builds of the build configurations. You can read more about in a blog post on artifact dependencies and dependent builds triggering.

And, finally, he mentions utility build configurations for revealing duplicate code and getting the Subversion repository statistics via StatSVN.

We are sure that you can make the most of TeamCity’s options when setting up your own build configurations selecting from a variety of triggering options, specifying dependencies between the builds artifacts and other build configurations and many others.

Wish you happy building, and, by the way, stay tuned to our blog Right now we are really busy discussing the next version features pool, so the roadmap is going to be published soon. Meanwhile, you can vote for the feature requests (and, of course, create new requests) at our new issue tracker and online forum.

Technorati tags: TeamCity, JetBrains, IntelliJ IDEA, Eclipse, continuous integration, build management, agile development, MS Visual Studio 2005, MS Visual Studio 2008

Hooray!

This year TeamCity has again received a Jolt productivity award in the Collaboration Tools category, and it is the first time we are recognized in Project Management Tools category!

IntelliJ IDEA - our flagship product - received an award for being a productive Development Environment.

We are very happy and proud that all our effort and work was not in vain and glad to see our tools get wider acceptance in IT world.

We would also like to congratulate and wish all the best to the other Jolt winners and Jolt judges and promise to keep on the good work

Technorati tags: TeamCity, Jolt, JetBrains, IntelliJ IDEA, Eclipse, continuous integration, build management, agile development, MS Visual Studio 2005, MS Visual Studio 2008

Even though TeamCity 3.0 brought a great deal of new features, it was long long ago - to be more precise - last year… Since then we got so much feedback and feature requests which we greatly appreciate and understood that we had to work harder A result is TeamCity 3.1 which is mostly a maintenance release but also brings a number of tasty features:

• Visualization of Build Agents’ workload
• “Time to fix tests” statistics report for monitoring the project health
• Improvements in 3rd party .NET tools integration
• More types of notification options
• Improved external database support (Oracle)
• Scope filter for Code Duplicates and Inspections browsers
• New options for builds triggering

Plus multiple user interface enhancements, performance improvements, and bugfixes.

Read the detailed What’s New page at the official website.

Download TeamCity 3.1 and let us know what you think at our forum.

As usual we have updated our public demo server, and you can try the new features of this release without any installation and configuration.

Good luck with your builds!

The JetBrains TeamCity Team

Technorati tags: TeamCity, JetBrains, IntelliJ IDEA, Eclipse, continuous integration, build management, agile development, MS Visual Studio 2005, MS Visual Studio 2008