TeamCity Blog

Yes, we admit that every so often TeamCity like any other application can misbehave or slow down for some reason you cannot understand, and traditional “close and open” method (or “shutdown and start” in TeamCity terms) does not always help to get rid of the headache…

Now you don’t need to spend ages when trying to diagnose the problem. We have created a utility for taking the CPU profiling snapshots of the TeamCity server right from the web UI. Download the latest version of this plugin and see the installation instructions for details.
And please note that it is compatible with TeamCity 3.1 and higher.

Have an untroubled building!

Technorati tags: TeamCity, JetBrains, Java, VCS, .NET, IntelliJ IDEA, continuous integration, build management, agile development, best practices, MS Visual Studio 2003, Eclipse, profiling, plugin

This post continues the story of new TeamCity plugins which have just appeared. Today we would like to tell you about two third-party plugins.

The Growl notifier plugin delivers alerts using Growl engine.

Another plugin named Team piazza displays the current state of the build informing the team when the build fails and provides much other useful information on the current build state.

We would like to remind you that anyone can become a member of TeamCity plugin development community and develop plugins for integration with different change management systems, build runners, IDEs, or notification means using TeamCity’s Open API. Get more information in TeamCity online reference.

Thank you very much for your effort!
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, plugin, Open API, extensibility

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

TeamCity 3.1 release is coming. And as we already stated, the release is targeted on the current features maintenance and critical bugfixes but we have also implemented some new features helping you to be more productive with your continuous integration process. Among the feature highlights we would like to name the following:

• New visual metrics for estimating the Build Agents workload and showing the time to fix the failed build tests
• Support for NAnt 0.86 Beta 1 testing framework
• NUnit 2.4 support
• Possibility to specify the mode (x86 or x64) to run the NUnit tests
• NUnit tests categories support for NAnt, MSBuild, and NUnit Launcher
• Reporting tests via standard output enabling smooth integration with unit tests
• Publishing build artifacts while the build is still running. As soon as the build produces a new artifact, it becomes visible and available for download and use in multiple places of TeamCity user interface
• Smarter notifications allowing to be aware on the first failed build after successful
  on the first successful build after failed and all company’s projects status
• Build Queue reordering is now available right on the Projects page
• Find the builds created on particular Build Agents and filter the builds history builds of particular build configuration typing a part of the agent name
• Filtering the code duplicates and inspections results by directories for better navigation in discovered issues
• Code duplicates are not dull looking any more as the syntax is now highlighted
• Improved cleanup options for saving the server disk space
• and many other fixes, polished user interface and improved performance

Download TeamCity 3.1 Release Candidate.

More technical details on this release improvements are available in TeamCity Reference. And as usual we want to ask you to backup your data before upgrading to a new version.

Wish you happy building!
The JetBrains TeamCity team

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

TeamCity and IntelliJ IDEA have been announced the finalists for this year’s Jolt Product Excellence Awards - an annual showcase of products that have the biggest impact on the software industry allowing to create software faster, easier, and more efficient.

TeamCity is nominated in 2 categories, namely, “Collaboration tools” (we were the winners in this category last year!) and “Project Management” tools.

The awards ceremony will take place on March 5, 2008 at the 21st annual Software Development Conference & Expo West at the Santa Clara Convention Center. We believe we have very good chances to win with our innovative approaches and rich functionality.

Keep your fingers crossed while the judges will take an in-depth look at us in the next round of the process!

Technorati tags: TeamCity, teamware, new version, JOLT, StarTeam, Subversion, Perforce, CVS, Clear Case, labeling, Java, .NET, continuous integration, agile

Alex Handy at SD Times, the industry newspaper for software development managers, in the article JetBrains TeamCity 3.0 Provides Visual Build Metrics, pays special attention to the statistic charts that help you evaluate build metrics at a glance. He also appreciates the two editions of TeamCity (free professional and commercial enterprise), and the new possibilities now available for the .NET users: search for duplicates and pretested commit.
Thanks to Alex for the positive feedback
Refer to the online documentation for details about statistic charts, editions and .NET support.

Technorati tags:
TeamCity, teamware,Java, .NET, continuous integration, agile