TeamCity Blog

In TeamCity 3.1 we are going to provide more visual metrics, namely, statistics for TeamCity’s Build Agents’ activity and their usage during a particular period of time.

Click the Agents tab and then go to the Agent Statistics tab to get an overview of the Agents’ workload:

When you mouse over the fancy-looking stripes, you can see the builds-related info such as their number, duration, and results in a popup.

Of course, the page view is customizable and you can specify the time range and sort the Build Agents display by their name and workload.

We hope you’ll find this feature helpful in:

• your daily administration activities for leveraging your company’s Build Grid
• bridging the gap between the most frequently used computers and those which are often idle and, finally,
• lowering the cost of your hardware resources ownership.

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

A flexible system of different build triggers in TeamCity allows to start the builds when it’s really necessary rather then use your company’s hardware resources at their most - running multiple builds at the same time and making you wait for the feedback on changes’ integration results.

Let’s now take a look at how TeamCity can help to “tame” builds clutter.

The most common case of firing a new build - changes committed to the version control system - can be altered by specifying a “quiet period” - time to pass with no changes in the build configuration VCS roots before TC starts a new build. In addition, you can use wildcards and operators to exclude parts of the VCS roots and ignore commits of particular users.

It’s quite common for many companies to create new builds periodically. In this case TeamCity can still limit the builds number if there are no changes pending to be built.

In TeamCity 3.1 which we plan to release soon, we’ve implemented more flexible build triggering options using Cron Expressions for more precise schedule tuning:

You can also specify to start a new build when a successful build of a dependent build configuration appears or when the previous build has failed.

In-depth build triggering options are, as usual, explained in online reference.

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

TeamCity 3.0 is almost here. While it is still in the oven, you can try this Beta release.
This is your last chance before the release to try the cutting edge version of TeamCity and let us know if you have any urgent issues.

Browse the release notes and download the Beta.

Happy building,
The JetBrains TeamCity Team

This EAP release brings:

• new user interface on assigning per-project user roles,
• redesigned Build Results page,
• possibility to create custom statistics charts,
• more powerful control on the build agents via authorized/unauthorized state,
• VCS labels for Subversion, StarTeam, and ClearCase, and more

The redesigned Assign roles dialog provides ability to assign a role in multiple projects:

Besides, it’s now possible to assign roles in multiple projects for multiple users and unassign multiple roles in a single action, and many others.

More possibilities on extending TeamCity are now available: report and display custom statistic values using teamcity-info.xml file. Statistics charts can then be displayed in the Statistics tab of the build configuration.

We have added one more state for the Build Agents for better control of the company’s Build Grid which is “authorized” Agents which can be managed by TeamCity Administrator. Only authorized Build Agents can run TeamCity builds. All those unauthorized immediately appear in Agents| Unauthorized Agents tab.

In addition to automatic build labeling, you can now label sources used for a build at a later time by clicking the Label this build sources link of the Build Results page:

Among the other improvements:

• smarter “Builds with my changes” notifications
• polished statistic charts presentation and new passed tests count and inspections/duplicates counts charts
• improved VCS support

View the more detailed release notes and download the latest build. And, as usually, we urge you to perform your data backup before upgrade and eagerly wait for your feedback.

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

In this EAP build we make the introduction to the role-based access to TeamCity features and also provide a number of improvements in other areas.

• The server administrators can now assign roles to users (available in Administration | User Accounts, particular user account page, Roles and Permissions tab):
  
  The already existing TeamCity users get the role of developers for all existing projects. You can find more detailed roles description in the release notes.
  In the nearest EAP releases we will improve the UI to allow assignment of roles to multiple users.
• The long-awaited VCS labeling of sources used in the builds is available for CVS and Perforce:



• Duplicates and Inspections runners now can accept Maven2 projects
• Pre-tested commit is supported for IntelliJ IDEA with StarTeam, ClearCase, and Visual SourceSafe version controls
• Duration charts can now be viewed for each unit test across multiple builds
• Search feature improvements: search by build tags and project/build configuration name is now available
• RSS feeds can now include only only the failed/successful builds or builds with changes of a particular user. The feature is accessible from the My Settings and Tools page:
  
• Possibility to set the frequency of querying the VCS for changes (configurable on the server-wide or a single VCS root basis)
• Ability to request immediate changes checking
• A new area on Administration page: a list of all VCS roots configured in TeamCity
• Support for different URLs for accessing the same SVN server from the TeamCity server and IDEs (no extra configuration is required)

View the more detailed release notes and download the latest build.

Technorati tags: TeamCity, JetBrains, Java, .NET, IntelliJ IDEA, continuous integration, build management, agile development, MS Visual Studio 2003, Maven2, Duplicates, Inspections, RSS

We are glad to announce the new EAP release of TeamCity 3.0. This release provides a number of useful and long-awaited features.

• Search by the build number. The found builds are displayed in a pop-up window, and you can also view the found builds on a separate page:



• A brand new feature: build tagging. The easy to apply labels help you to better organize the builds history and quickly navigate to the builds marked with the specific label. You can apply multiple tags for a single build, for example, “EAP”, “release”, and others:



• Possibility to take the thread dumps for both Java and .NET build processes. This new feature helps to investigate the problems of the currently running build right from the web UI:



• Numerous statistics-related improvements:
  • Builds range and status filters added
  • Code coverage statistics graph is added with 4 series for class, method, block, and line coverage
  • Build sources checkout time now can be extracted form the full build duration time and is displayed as a separate Clean build duration graph:

  

• Subscription to the finished builds RSS feed of the selected build configuration to help you stay up-to-date with the current projects status. Click the Subscribe link located at the bottom of the build configuration page and configure your feed reader to monitor TeamCity builds RSS.



• Several VCS-related improvements:
  • per-VCS root user names (possibility to set a specific username for each VCS root)
  • VCS trigger quiet period: TeamCity triggers a build only if there are no changes for the specified time in all VCS roots of a build configuration
  • VCS triggering filters by VCS user and VCS root (allows to prevent build triggering after changes submitted by a particular user or changes from a specific VCS root)
• Miscellaneous improvements including ability to view a web diff for personal changes, ability to edit TeamCity server URL through the web UI and VCS roots attaching from the project’s page.

And as usual, the new release includes multiple bugfixes and performance improvements.

View the release notes and download the latest build. We eagerly wait for your feedback at our discussion forum.

Technorati tags: TeamCity, JetBrains, Java, .NET, IntelliJ IDEA, continuous integration, build management, agile development, MS Visual Studio 2003

Even though it’s a holiday season now, we keep on working here, at JetBrains, to bring you more features you want to be implemented and asked for. So, after several weeks of hard work a new TeamCity 3.0 EAP build is available!

This EAP features highlights:

• .NET projects code quality improvements: search for code duplicates for C#
• the so-long awaited statistics: view the builds’ duration, artifacts’ size, and code coverage trends



• downloadable build log (available in text format)
• enhanced customization possibilities for build results: build status and its description, and the build number can now be modified by the build process
• MSBuild build runner improvements: support of MSBuild build started from within the NAnt script (by NAntContrib msbuild task. For more details, please access TeamCity documentation)
• in addition to supported NUnit2 task for NAnt, we have improved the already existing support for NUnit task of MSBuild (from the MSBuild Community Tasks project). No need to modify existing scripts to run them under TeamCity: get the improved output automatically.
• build tests view allowing you to view how long each test ran, their status and other info and sort them out simply clicking the desired column



• remote run and pre-tested commit for MS Visual Studio 2008 Beta 2

View the release notes and download the latest build.
We wait for your feedback in our discussion forum.

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

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 start and finish times
• Possibility to assign agent to specific build configurations
• Detection of hanged builds
• Multiple UI improvements

and other issues.

We have much more plans, with primary focus on statistics and per-project access rights. Stay tuned with Benares early access program.

Download TeamCity Benares EAP build

Kind regards,

—JetBrains TeamCity team

TeamCity, JetBrains, continuous integration, build management

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 build management. Partially, we are doing this already and TeamCity currently offers:

• a set of tools for improving code quality (using powerful server-side code inspections and duplicates finder from the best Java IDE around)
• tight integration with various IDEs and possibility to navigate from Web UI to the source code
• web-based access to user changes, including diff
• time-saving team communication regarding failed builds

But we have more plans.

• Managers (and not only managers) like statistics and nice charts. What are the project coverage trends? How build duration changes? Shall we use more build agent machines to reduce waiting period for builds in queue?
• We’re going to provide code inspections and duplicates finder for Eclipse projects and for Maven projects
• Add possibility to view list of changes for selected users, calculate commit statistics, browse project source tree
• Many our users ask for delayed commit functionality in Visual Studio with Subversion repository
• We plan to implement per-project access rights

From the other hand, we aspire at providing best on the market continuous integration and build management solution. It is not easy to find new features in this area, but we believe it’s worth trying:

• Multiple VCS configurations within single project with possibility to include/hide particular directories in the source tree (cloaking)
• Composed builds with parallel execution on different OS platforms. Final build status will depend on composite status of the builds.
• Possibility to take a thread dump from the build agent right from the Web interface when tests hang.
• Support for blinking tests. Do you know those annoying tests which fail, well, sometimes?
• Edit build agent properties remotely, via Web UI
• Advanced build promotion action with possibility to publish it to external location, pin, tag, prepare changelog, and execute arbitrary script
• Starteam VCS support
• more

Surely, these are just plans. And this is just the tip of the iceberg. But we will try hard to implement most of the features. Despite of the vacation season :).

Work is in progress. We invite you to participate in the discussion of the features and to vote for stuff most interesting for you. Here are some resources for that:

• Benares RoadMap in the TeamCity EAP wiki
• TeamCity support forum

With kind regards

—JetBrains TeamCity team

TeamCity, JetBrains, continuous integration, build management

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 Maximov

Technorati: TeamCity, JetBrains, eap, continuous integration, Subversion