TeamCity 9.1 EAP4: Countdown for Release

This is probably the last EAP build before the 9.1 release planned for the next week.

Comparing to the previous one, it has SBT runner plugin bundled and it defaults to not using server-to-agent HTTP connection anymore (details). The build has an RC quality and is recommended for the test servers.

It's your last chance to try pre-release TeamCity 9.1 and notify us if anything goes wrong with it!

The build already have no EAP license key bundled, so let us know if the server switches to professional mode on upgrade.

Stay tuned for the release!

TeamCity 8.0 RC Build #27390: Almost There

We plan TeamCity 8.0 release for for this (or at most the next) week and here is the last chance to try pre-release version on your server and let us know if it plays nicely in your environment.
The build is of release candidate quality so give it a try today!

Here is a list of fixed issues and one of them is pretty interesting: TW-16735 Allow to use more than 20 build configurations for less than full TeamCity Enterprise price.

And that one is actually implemented in 8.0!
Weighting several options we decided to go with the one to make each build agent license also add 10 build configurations in addition to one agent. This obviously applies only to Professional edition. All the agent licenses valid with TeamCity 8.0 will add 10 build configurations each once you upgrade.

Hope you will find this useful as well as other 8.0 features.

TeamCity EAP build #23892: 7.1 is Almost Here

We plan to release version 7.1 around next week, so this is really close: build 23892.

There are no major changes, just bug fixes and some polishing before the release. If you plan to upgrade to 7.1 when it will be released, it makes sense to try this EAP build to see how well it plays in your environment. In particular, if you plan to use the new feature branches support, make sure to try it out.

 If you encounter any critical issues, please let us know the details via teamcity-feedback at jetbrains.com so that we still have chance to address it.

Please note that this build does not have EAP license key bundled already. You can get evaluation key on the official download page.

TeamCity 6.5 RC: Days For the Official Release

Here is a build that is one tiny step before the official 6.5 release. It has just several bug fixes over the previous one and is meant to be the last chance to try a build before the release.

If you consider upgrading to 6.5, consider trying the build and warning us on any misbehavior found.

A hint: this build still has an EAP license bundled (valid for 30 days) so this can be yet another reason to download and try it :)

In the mean time we are starting to think what could we bring in TeamCity 7.0 and you might add your thoughts as well :)

TeamCity 6.0 RC2 (build 15700): Changes Filter in Schedule Trigger and Fixes

As one more bit before the release here is a RC2 build.

It has only several noteworthy changes and some issues fixed.

A little but wanted feature still slipped in at this time: ability to make Schedule trigger skip triggering a build if the pending changes match specific pattern.

Please note that this build comes without bundled EAP license key (but you can still get one form previous EAP build if you wish :).

Want to get a preview of the almost ready TeamCity 6.0? Jump on the train.

BTW, if you happen to still have TeamCity 4.x installed, you might want to consider buying an upgrade before 6.0 comes out (you can count days now). This way you can still get upgrade discount and get 6.0 and (as with a usual license) get all following releases within a year included into the price.

TeamCity 6.0 RC1 (build 15673): .Net coverage and other improvements

As the release is close we are trying to share the current TeamCity state more frequently with you.

The version has "RC" in the footer to denote close release, while we are still working on fixes and minor improvements.

This release moves Swabra settings out of the build step settings into a new place called "Features". The "Features" section will also get XML test reporter settings soon. This new section is designed to hold settings not specific to any particular build step, but participating in the build behavior.

If you have a plugin for TeamCity which affects build behavior but is not specific to a build step, you can consider moving plugin settings into the section. See the sources of the mentioned plugins for an example.

For this build's changes review, see the release notes or dive into resolved issues in the tracker.

As we are approaching release we are extremely interested in any upgrade and stability issues with this build.

Want to ensure seamless upgrade of your setup to final TeamCity 6.0? Try upgrading your data with a test installation of this RC.

PS I was a bit quick to announce some surprise feature in the previous EAP post. Unfortunately, we decided to postpone it till future releases since it will require some more work (and your feedback too!)

TeamCity 5.1 RC2: build 13340

As release is really-really close, here is one more RC build.

It has some issues fixed and also has SourceGear Vault plugin bundled with "experimental" status.

Please backup, download, report.

And we are back polishing the build to remove that "candidate" from it's current "RC" name.

New build (8909): Release Candidate

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.

TeamCity 3.1.2 Release Candidate

Since the 3.1.1 release, thanks to our users, we discovered and fixed some bugs in the code. The most critical ones were integrated into 3.1.x branch and now it's time to release the fixes as 3.1.2 release.

Before the release we would want to check that the fixes really work and no new ones were introduced, hence the 3.1.2 release candidate.

In this release we have included:

• reworked clean checkout for VSS which now uses native client instead of glitchy VSS API;
• reworked build stopping logic under Linux platforms: we no longer use JNI (to find out the PID of the current process), but some command-line magic;
• reworked database migration tool. OutOfMemory error on large databases is (hopefully) fixed now, as well as data truncation errors. Also, detailed progress reporting is implemented which is really useful when migrating large setups.

  Nevertheless, for a production use please consider migrating to one of supported external databases as soon as possible;

• fixed security issue when a user watching "All Projects" may receive notification for a project he/she does not have access to;
• miscellaneous fixes in CVS and StarTeam support, other issues.

So, if you are still using TeamCity 3.1.1 or earlier and did not upgrade to Calcutta EAP, please try this release candidate build.

Those using the 4.x branch EAP does not have the option to try this build because the TeamCity data directory was already upgraded to a newer format and it cannot be downgraded. On the other hand, most of the fixes were already available in the latest Calcutta EAP and the most recent ones will be available in the next.

PS
While preparing the release notes for this release candidate I approached the team developing our home-grown issue tracker with a reminder that the tracker still has no way to make an external link to a shared folder like "3.1.2 fixes". 30 minutes later we already had the new version of the tracker deployed with the feature added. "Wow", said I and grabbed the link for the 3.1.2 fixes.
Not having the feature beforehand is the cost, but ability to have a feature added in the matter of minutes is the benefit of using in-house developed solutions.