TeamCity Dev Blog

Teamcity 4.5.4 bugfix release is ready

2009-07-08T18:13:00.002+04:00

We've decided to release one more minor update to 4.5 branch to cover the issues found recently.

Please download it form the official site.

The list of the fixed issues can be found in the tracker.

Expect EAP for TeamCity 5.0 (codename Darjeeling) coming in a week or so.

TeamCity 4.5.3 is here to fix 4.5.2

2009-06-16T20:21:00.002+04:00

It happened that 4.5.2 release had Rake runner nonfunctional :(

Sorry about that. We fixed the issue right away but need to provide updated distribution so that less users are affected.

So here it is: TeamCity 4.5.3.

The main development is already done in to-be-5.0 trunk but for the week since 4.5.2 release we integrated several fixes and improvements into 4.5.x branch. Here is what our tracker reports for 4.5.3.

BTW, "Cheers" to all the users who showed up at our JavaOne booth. Thank you for the feedback and do not hesitate to post and discuss more in the forums.

Teamcity 4.5.2 is available

2009-06-09T13:30:00.003+04:00

Hello everyone,

The second update of TeamCity 4.5 is available for download.

The list of changes is available in our tracker and on our main site.

This build contains an updated version of SVNKit library (1.3.0), so it should behave more nicely with Subersion 1.6 repositories.

Let us know about issues found, if any.

Kind regards,

KIR

Meet us at JavaOne

2009-05-25T11:49:00.000+04:00

Want to meet in person with guys behind TeamCity, IDEA or MPS? Eager to see the products in action or describe pain points? Come to JetBrains booth at JavaOne (June 2-5).

TeamCity 4.5.1 is released

2009-05-07T20:16:00.002+04:00

Fixed bugs: http://www.jetbrains.net/tracker/issues?q=state%20fixed%20fix%20for%20Calcutta%204.5.1%20(8975)

Download link: http://www.jetbrains.com/teamcity/download/index.html

TeamCity 4.5...

2009-04-23T17:15:00.001+04:00

is live.
Time to think about new features and plans. Any suggestions?

TeamCity Git Support from JetBrains

2009-04-17T21:14:00.003+04:00

One of the most requested version control supports in TeamCity is Git. We do not (yet?) use it ourselves but were a bit affected too because most of the Ruby projects we setup on teamcity.jetbrains.com to demo our Rake runner were moved to Git and we could not build them anymore.

There was a git-teamcity project on gitgub, but it seems that the first author lost interest before it took off. Luckily, it was branched by Chris Ortman and the first working Git plugin for TeamCity appeared some time after. The plugin was installed on some public instances like CodeBetter.com.
AFAIK the plugin uses agent-side checkout and relies on git binaries present on TeamCity server and agent machines.

After IDEA officially received Git support we got a chance to devote time to adding Git support to TeamCity. IDEA integration is based on git binaries but JGit was chosen as an integration method for TeamCity plugin.

Quite naturally, TeamCity Git plugin sources were put into Git repository. Thanks to Git distributed nature it was no problem to start with local repository on the developer's local machine and then push the changes to public repository without any special treatment to save the history.

Several weeks ago we installed the Git plugin in our internal TeamCity installation and started to build the plugin with TeamCity. Today we upgraded teamcity.jetbrains.com to just released build (4.5 RC), added the plugin and now are able to build the plugin so everyone can have access to the most recent version in the best traditions of CI.

Everyone is welcome to try the plugin and send us feedback.

Please note that the plugin is in EAP stage, so critical issues can be encountered. Please also ensure you have the latest TeamCity EAP build as the Git integration plugin is not compatible with previous versions.

New build (8909): Release Candidate

2009-04-17T21:14:00.000+04:00

We plan the release for the next week and here is a release candidate build. As one of the last changes we decided to perform rename refactoring on the version itself. With all the features and improvements since 4.0 we decided it can deserve to be called 4.5 instead of 4.1.

The only change we forgot to commit is a version displayed in the TeamCity footer: if you see 4.1 there distrust your eyes, it's 4.5, but masquerading :)

So, what's new?
- reworked tests grouping on the tests tab
- further improvements to LDAP synchronization (anyone to describe LDAP configuration to test completeness of our settings?)
- fixes, improvements and fixes again.

More in release notes.

If you try the build (please do), let us know about any issues uncovered in your environment.

Subversion labeling for googlecode projects

2009-04-11T13:54:00.004+04:00

This is a small hint for those who host an open-source project on code.google.com.

If you want to setup TeamCity VCS labeling for your project, use the following in your SVN labeling settings field:

/trunk=>/tags

and don't forget to specify authentication information for your SVN settings.

New EAP build (8870): Boosted LDAP integration

2009-04-06T23:25:00.002+04:00

With several last-minute fixes to LDAP integration (so last-minute we are are providing them as a separate download - see the note on Download Page), we are releasing the next EAP build from 4.1 series.

LDAP integration can now retrieve user details and groups membership as well as automatically create users in TeamCity once they appear in LDAP. The latter feature is useful for sending builds notifications to the users that do not even know about CI server.

With more UI polishing and bulk group operations, user groups feature is almost finished in this build.

A detailed changes description can be found in the release notes.

If you care either about user groups or LDAP integration please give these features a try and let us know your opinion. We plan to release 4.1 in several weeks and there is still a chance to fix major issues if you spot them.

Cumulative JetBrains Products Update

2009-04-01T13:58:00.002+04:00

If you do not know already, today we are announcing a pack of new features to all JetBrains products.
Please welcome TeamCity's Cash Options,
IntelliJ IDEA's Voice Control Plugin
and ReSharper's Configurator.

TeamCity Tracker Upgrade

2009-04-01T11:32:00.001+04:00

About a year ago we migrated our TeamCity issue tracker from JetBrains Jira to a new tracker that is developed in-house. The dogfooding is great - the developers are several rooms away and you can always go complain in person rather then trying to write everything down :)

The tracker (its codename is Charisma) has been evolved a lot since then, but there were no changes visible for the last couple of months. Why? Because of the new completely rewritten UI and the whole new approach to replace the current one. These changes could not be done incrementally and were developed under cover for quite a while. BTW, the ~~language~~ technology behind Charisma is MPS and that makes the development much more fun.

A week ago a new update was pushed to www.jetbrains.net/tracker and now all the users can try the new UI themselves. The old one ("workspace") will be abandoned soon.

So head to your profile ("Settings" tab) in the tracker and check "Use New UI" checkbox.
You will then be redirected to new UI URL: www.jetbrains.net/tracker/issues.

The workspace can still be reached by www.jetbrains.net/tracker/oldWorkspace, but if you ever need it - let us know why. We will need to improve new UI before we drop the old one for good.

Do you like new UI? Any difficulties using it? We need your feedback! Found a bug? Post it right into Charisma.

Plugins are Fun

2009-04-01T09:54:00.002+04:00

Just to let you know that we've updated a plugin that you might need today.

VAN meeting: TeamCity Live Demo

2009-03-31T21:59:00.000+04:00

Zachariah Young kindly invited someone from JetBrains to present at one of the Virtual ALT.Net online meetings about TeamCity. We accepted and will be giving a demo this Wednesday.

Virtual ALT.Net is a virtual group that meets once a week to talk about different alt.net topics. Current topic is on automated build and continuous integration.

More details in Zachariah post.

It will be early morning in Saint-Petersburg, but I will try not to fall asleep :)

New EAP build (8804): XML reports, support P4 in VS, more tests analyzing tools

2009-03-19T16:42:00.000+03:00

During this week we were trying to get a build that we would consider EAP quality.

But as soon as one issue was fixed, another poped out and that delayed the EAP release at least half a day more. Our full build cycle takes about 4 hours. This includes many steps from Java and .Net code compile through unit tests on 4 platforms and and 5 different environments to assembling distribution packages. This process is split in about 20 steps (build configurations) and we share a common build factory with IDEA, ReSharper and other JetBrains products, so a full cycle make take a while.

Finally, after some battles we grabbed a build and are throwing it into EAP: build 8804.

Be sure to read through the release notes as it may expose unusual behavior in respect to user's default settings - read the yellow block in the notes for details.

One of the highlights of the build is bundled XML report plugin. The plugin was available for several months as a separate download and now it has reached the state we can bundle it into the distribution. But be sure to add tests reporting only if you do not see test in TeamCity UI already. Otherwise, you will get each test reported twice: once by automatic TeamCity listener and another from the XML report.

Have PMD or FindBugs reports generated during the build? Configure the report importer an get the results in TeamCity inspections browser empowered with "open in IDE" functionality.

Use Perforce and longing for the Remote Run functionality in Visual Studio? Now you get it.

Need a bird-eye view on a test in the scope of the entire project? Test details are now project-wide.

Badly want another feature? Go vote for it in our tracker (or submit a new one).

As usual, your feedback is highly appreciated.

4.1 EAP is open

2009-02-20T21:11:00.001+03:00

Let us share the results of our last months work on TeamCity. We branched on 4.0.x and 4.1 releases about the same time 4.0.1 was released, and the main work effort is undergoing in the 4.1 branch since. We were continuously upgrading the internal TeamCity installation (and fixing emerging issues right away). As we reached a certain point in features and have quite stable build, we are ready to make the build public.

You can read through the release notes to get overview of the changes.

One of the main features we are introducing is user groups.
Groups store users and can be assigned roles, just like users. A user then gets all the directly assigned roles and all the roles assigned to the groups she belongs to. A group can contain other groups and users, it can also be included into several groups. Currently you can assign roles and add users on the group details page.

Our nearest plans are to add notifications to groups - they will work as default notifications for all the members of the group. Also under way is LDAP integration with automatic retrieval of user-groups correspondence from LDAP.

Please let us know your groups usage scenarios so that we can consider them when enhancing TeamCity groups support.

Get the build from EAP download page. And let us know what you think about the new features participating in the poll to the right.

TeamCity 4.0.2 is out

2009-02-03T11:05:00.066+03:00

Our download page has got a new update with 4.0.2 link.

As we are working on 4.1 since about 4.0.1, so 4.0.2 is a branch which got only critical bugfixes and urgent improvements.
Generally, you will want to upgrade from 4.0.1 to 4.0.2 if:

you are using snapshot dependencies and spot build queue growing large with automatically triggered builds of the same build configuration (now we merge them more aggressively)
you often have builds with lots of failing tests (performance fixes)
you are using SVN (several fixes incl. performance)
you are using CVS (fixes in pre-tested commit from IDEA, other)
you use TFS with large repositories and experience performance issues (we added TFS agent-side checkout, it is a bit experimental, though)
you are using MSTest reporting (stability fixes)
you have extra large build numbers (we increased the length from 32 to 256 symbols). In the trunk we also truncate build numbers in web UI to make them usable. This will soon be available in 4.1 EAP
or if you experienced one of the fixed issues

Need user groups support? Want to move a build configuration from one project to another right from the web UI? These are the features already in development for upcoming TeamCity 4.1. We plan to open EAP for it in a week or so.

Linking JavaDoc from Confluence

2009-01-16T21:47:00.003+03:00

If you hadn't yet noticed, our Plugin Development documentation got a major boost recently with new topics and more detailed descriptions.
Today the documentation got links to online openAPI JavaDoc.

It seems there is no generally available solution for the JavaDoc links in Confluence, so here is a description of our approach.
The links were accomplished via Confluence User Macros

Now when a Confluence wiki markup looks like:
{tc-javadoc:jetbrains.buildServer.serverSide.SBuildServer|findBuildInstanceById(long)}
it is turned into a link: jetbrains.buildServer.serverSide.SBuildServer#findBuildInstanceById(long).

The User macro is:


#if ($param1)
  #set ($methodRef = "#$param1")
#else
  #set ($methodRef = "")
#end
<b><a href="http://javadoc.jetbrains.net/teamcity/openapi/current/${param0.replaceAll('\.','/')}.html$methodRef">$param0$methodRef</a></b>

Additional macro options:
Macro has a body: OFF
Output: Macro generates HTML markup

This is macro's first and quick version, it will probably be enhanced along the way.

TeamCity 4.0.1 is released

2008-12-26T18:15:00.000+03:00

Christmas in Russia is celebrated in January, so this gives us an excellent opportunity to work and even release TeamCity in the middle of Christmas holidays in US and Europe.

Here you are. TeamCity 4.0.1 is out.

Our tracker can let you know the full fixed issues list.

Merry Christmas and Happy New Year!

4.0.1 EAP, build 8111

2008-12-05T18:12:00.000+03:00

Here is a new build to open the EAP program for 4.0.1 bug fix update.

Search results highlighting, build queue and notification calculation speedups, possible (but rare) deadlock fix - these are some of the changes in the build.

Currently we do not make any major changes focusing on important or small changes in the code, so the build should be quite stable.

BTW, did you notice what's special in the build number?

And the winner is...

2008-11-27T23:26:00.000+03:00

Build number 8080!
Congratulations, you've just been promoted to the official TeamCity 4.0 release build.

The most advanced continuous integration for Ruby on Rails with TeamCity 4.0

2008-11-27T23:13:00.000+03:00

TeamCity 4.0 has a dedicated rake runner, with support for Rake tasks, Test::Unit, and RSpec tests.

Our special thanks goes to the guys behind RubyMine and Ruby plugin for IntelliJ IDEA, who created this runner for TeamCity.

Here is a short (3.5 min, 7.3Mb) demo of some unique TeamCity's features and how they work for a Ruby on Rails project.

This demo includes:

setting up Rake runner build configuration
running a build, with progress estimate for subsequent builds
ongoing test reporting while build is running
viewing changes in version control, which are included into the build (web diff)
"first failed in"/"already fixed in" features for failed tests
full sortable test list for a build
a graph for test duration time

View demo

Read more about TeamCity features and what's new in 4.0 or download it now and see for yourself!

Regards,

KIR

A chance to try almost TeamCity 4.0 before the official release

2008-11-20T22:24:00.003+03:00

We've published build 8018 which is separated from the official release build by only a couple of build number increments.

Don't miss your chance to try it and be fast to let us know if you spot any critical issues with it.

How ReSharper found a bug in IDEA with the help of TeamCity

2008-11-03T17:50:00.000+03:00

A history of one bug.

Several days ago, I received a message from one of ReSharper developers:

The link opened our internal TeamCity installation with the ReSharper build failed on sources checkout. The error was produced by SVN unable to update a directory:

svn: Failed to add directory 'test/assemblies': a versioned directory of the same name already exists

After some digging it turned out that the directory was deleted from the repository some time ago but was not deleted form the build agent. Then it was added anew and the build failed trying to add a directory that already existed on disk. The workaround was to invoke "Enforce clean checkout" from the TeamCity UI for the build configuration.

So ReSharper team can continue their current development effort on performance optimization, but why the directory was not deleted in the first place?

TeamCity uses SVNKit library to talk to Subversion repositories and luckily the developer of the library happened to be just a room away these days. Introduced into the issue he reached for the code to check and soon found a bug in the library that might result in not deleted directory in the working copy. It could only reproduce under certain optimization options that only two products are actually using, one of them being TeamCity and the other ... IntelliJ IDEA. But wait, IDEA is preparing for the 8.0 release these days!

No worries. As I am writing this, the library is already fixed, the latest build downloaded from SVNKit TeamCity installation and as I've just checked on our TeamCity server, the fix is already checked into IDEA release branch.

Actually, the bug is a rare one since it can reproduce only under certain circumstances, it was introduced not so long ago and was only included into EAP releases of IDEA and TeamCity.

Calcutta EAP, build 7888

2008-11-01T19:25:00.001+03:00

A new EAP build was published on Tuesday.

The main changes are described in our EAP space, but there were many others and I will point out some:

Connected agents now display the time of last activity rather then time of registration on the server;
Presentation of Test Details page has been improved;
"Triggered by" field of the build now displays the build configuration name if triggered by same-sources dependency;
Storing of duplicate code finder results has been improved. The results are now valid for all the builds. Previously, the duplicate results were only valid for the most recent build and older builds could show incorrect data;
If you write a build script or tool and need to detect whether it is run under TeamCity or not, you can now use TEAMCITY_VERSION environment variable that holds TeamCity version as shown in the web UI footer;
IVY library has been updated. We use it to resolve artifact dependencies on agents. The updated version properly handles spaces in the file names, at last;
Logging of VCS-related errors into the TeamCity logs has been improved to be less verbose but note more details;
Windows build agent installer no longer defines JAVA_HOME to point to bundled JRE. This will make the administrators make an explicit choice if their builds use JAVA;
Build stopping logic has been improved under Windows to eliminate wrong process tree building when process ID was reused by the OS;

Grab you copy of the fixes on the download page.

As always, your comments are welcome!