TeamCity 10 EAP is Open

Our current plan is to release TeamCity 10 in the summer and we are working on the new features for several months already. Today is the time to share our current progress.

As we follow our tradition to code-name major releases after Indian cities in alphabetical order, we have chosen "Indore" as the next codename, so Indore means TeamCity 10.

Here is the first preview of the upcoming TeamCity 10 / Indore, build 40941.
Check the release notes and give it a try on test server.
We run the build on the internal JetBrains production TeamCity instance, but since this is not a released version, it can only be used for test servers, not production ones.

We are open for any feedback on the features announced in the release notes, let us know if you have anything to say about it.


Since this blog has turned into TeamCity announcements-only long ago, I am thinking on dumping it in favor of the official blog at http://blog.jetbrains.com/teamcity/
If you do not like the move, make sure to describe why in the comments here.

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 9.1 EAP3: Approaching Release

We plan TeamCity 9.1 release for July, so this is one of the last EAP builds which is approaching release quality. We run nightlies on our internal TeamCity instance for a long time already and have just upgraded public test instance https://teamcity.jetbrains.com/ with the build.

The build introduces experimental ability for one way agent-to-server communication and bundles VSTest support which was previously available as a separate plugin. For details check the release notes or full list of fixed issues.
Apart from that we are mostly focused on polishing of the earlier introduced functionality and fixing bugs.

It's high time to try the build on your test servers and drop us a line if you find any issues with it.

BTW, if you missed the results of the TeamCity plugins contest, make sure to check the winners and all the participants on the plugins page.

TeamCity 9.1 EAP2: Per-Build Step Settings, Build Log Color and More

Last week we have prepared a new build sharing our current development effort in the scope of upcoming TeamCity 9.1: build 36518.

Check the release notes or full list of the fixed issues.

Get the build from the EAP page.
While the build is stable enough to build all the JetBrains products, it is not recommended to upgrade your productions servers. Trying the build on a test server is the way to go. Please note that the build updates the Data Directory structures so downgrade of the data is not possible.

We target 9.1 release for July, so the started features are stabilizing and get polished. Don't miss your chance to let us know your experience with this EAP build. Report issues into the tracker and leave feedback in the forum.

TeamCity 9.1 EAP Opening: Custom Sorting for Projects and More

Here is the first preview of the upcoming features in TeamCity 9.1.

The major visible addition is ability to set custom display order for the Build Configurations and Projects lists. The world is no more alphabetically sorted!

If you use Perforce or Subversion you can now store Project and Build Configuration settings in the version control, just like you could in Git and Mercurial since TeamCity 9.0.

And there are more. Check the full release notes. Or full list of fixed issues.

The build has all the fixes included into 9.0.4 release and is stable enough for our production use within JetBrains.

There is an EAP license key bundled which is valid for 60 days. This way you can install it on a test server and try it for the time. We will release the next EAP build within the license time.

TeamCity 9.1 is currently planned for the mid-summer, we still have time to add some interesting features.

Download,  install on a test server and let us know your feedback or any issues you face in the tracker.

TeamCity 9.0 EAP5/RC (build 32023): Final Polishing

This is one of the last public builds before TeamCity 9.0 release so we encourage everyone to try it on your test servers. This build should also be suitable for not large production servers.

If interested, you can review the full list of fixed issues in this build.

Grab it,  install it and let us know about any issue you find in the issue tracker.
This is your last chance to report us any issues that can still be fixed in the final 9.0 release.

TeamCity 9.0 EAP4 (build 31963 ): Approaching 9.0 Release

Here is a new current TeamCity development preview shared as EAP release.
Check details on the new features and try it on your test servers.

Since we target 9.0 release within a month, it's high time to try the build and let us know how it works in your environment and how well the new features cover your needs.

Keep us posted on your findings in the forum or the issue tracker.

TeamCity 9.0 EAP3 (build 31886): Project Import and More

Here is a new current TeamCity development preview shared as EAP release.
Check details on the new features and try it on your test servers.

Since we target 9.0 release within a month, it's high time to try the build and let us know how it works in your environment and how well the new features cover your needs.

Keep us posted on your findings in the forum or the issue tracker.

Check What's Upcoming in TeamCity 9.0 before the Release: EAP2 (build 31717)

Sorry for the late announcement here, I was out of the office last two weeks visiting JavaOne and some of our customers in the Bay Area.

A new EAP build for the 9.0 code line was published last week.

Check the changes and give it a try on your test servers. We appreciate any feedback on the new features and how their current state applies to your scenarios. Your comments here, posts in the forum or email messages are welcome! Especially taking into account that we target 9.0 release for the end of November your feedback would be very useful at this time.

Looking through the summary of the last week's customer visits, the general product feedback is very positive. There is always room for improvement which we like to fill making TeamCity experience even more smooth and pleasant.
If you do not happen to be in direct contact with us - we are always open for your suggestions and ideas, so if you have thoughts to contribute - make sure to share and discuss those with us.

TeamCity 9.0 EAP is Open

We have published a EAP build corresponding to the current state of the TeamCity trunk development. This will become TeamCity 9.0 in a couple of months according to our current plans.

The code name for TeamCity 9.0 is Hajipur (which is an Indian city starting with H according to our convention).

A note on stability: we run the build on our internal JetBrains installation of TeamCity, but I would not recommend upgrading your production servers to the EAP build. Consider using a test server.

For the overview of the new functionality in this build check the release notes. We would be glad if you find time to try the build on your test servers and let us know what you think on the features and their implementation approach.
You can also get a full list of addressed issues in our issue tracker.

There are also a couple of topics we are working on, but which are not yet reached a state allowing to try them. These include ability to move projects between servers (including build history), performing daily cleanup completely in background, and some more. Also, there are several plugins in the works which are likely to be bundled soon. These include integration with VMware vSphere like that for Amazon EC2 and integration with Sonar.

The features announced in this EAP as well as the above-mentioned ones will form the core of the TeamCity 9.0 release and we will likely spend the rest of the time polishing them, with only some minor features additions.

What do you think on the proposed 9.0 feature set?

TeamCity 8.1 EAP Build #29790: Build Artifacts, Backup/Restore Improvements and More

We are targeting 8.1 release for February, so here is one of the last EAP builds before the release. It includes several new features like ability to configure build artifacts via selecting paths in UI, improved backup and restore performance and more. For a full list of fixed issues, check the tracker.

This version comes with a bundled EAP license key which will be removed in one of the next public builds, so it's a good chance to get a build and use it for several months without build configurations or agents limitations before deciding to upgrade the licenses.

Get to the download and do not forget to report any found issues to us via the forum or the issue tracker.

TeamCity 8.1 EAP Build #29687: Better Templated Configurations Customizations and More

Here is a fresh update from the current TeamCity development for the version 8.1. It includes further enhancements in the first build creation experience and allows to override most of the options coming from the build configuration template in place. hose like build number format or failure conditions.

Check the release notes for complete overview of the new features.

If you plan to upgrade to 8.1 when it becomes available, consider getting this EAP build to evaluate the features and let us know your feedback so that we can still incorporate it into the release.

The forum and the issue tracker are at your disposal!

TeamCity 8.1 EAP Build #29581: Easier Setup, Investigations in REST API, VS 2013 and More

Here is a new build with the current state of our movement towards 8.1 release.

We continue to improve TeamCity configuration, now with ability to create a VCS root based on single URL and revamping Build Configuration administration UI sections. While can seem unusual at first, these changes should serve for better unification and clarity.

Those of you who use TeamCity REST API might find useful the recent additions on reading assigned investigations and listing build queue as well as build triggering.

Keeping up to date with the tools releases we make TeamCity compatible with Visual Studio 2013 and add support for agent-side Subversion 1.8 checkouts.

See more details in the release notes.

Our current plans for the final 8.1 release were adjusted a bit and we now target February, 2014 for the release. With your feedback on the recent additions we will be able to deliver a great release for the time.

Go grab the build and let us know what you think in the forum and issue tracker!

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 8.0 EAP Build #27147: More Nested Projects, Meta Runner and More

We target TeamCity 8.0 release for June, so we are approaching features finalization and polishing stage. This EAP build can give you a good overview of the major features coming in version 8.

These include:
- nested projects for presentation and settings propagation;
- human-friendly "external" ids for all the settings entities: projects, build configurations and VCS roots;
- meta-runner for reusing sets of build steps with custom UI (see example);
- health report for identifying configuration and other issues;
- DVCS-related improvements like support for reporting changes from Mercurial subrepos and filters for branches in triggers

This is not to mention significant improvements in cleanup procedure and tons of other fixes.

You can get details on the latest changes in the build's release notes and get the build to try on a test server.

If you are interested in any of the mentioned features, it's high time to try EAP and give us your feedback, so that we still have some time incorporating it into the final 8.0 version. BTW, if your thread in the forum does not get due attention from us, feel free to post a link to the comments of this post so that we get additional notificaiton.

TeamCity 8.0 EAP Build #26816: Friendly Ids for Projects, Mixed Authentication and More

We aim to release TeamCity 8.0 in 3-5 months and so it's time to open EAP for the version.

Today you already can try what we have in place and give us feedback for the features.

The most prominent are:

Human-assignable projects ids. These will be used in web UI URLs and REST API as well as in the settings files under TeamCity Data Directory. Ids for the build configurations are to follow.

Ability to have several authentication modules at once. This is useful for migration from one user authentication to another and for giving more freedom in setting up authentication.

TeamCity plugin for IntelliJ IDEA has also got a couple of features which we eagerly awaiting feedback for.

Please look through the entire change log to get an overview of all the new additions.

We have the build running on our internal production TeamCity installation for quite some time and it works good for us. However, please install the build as a test server. The version converts the settings and the database to a new format and you will not be able to downgrade the server to version 7.1.x, only to upgrade it to the following EAP builds and TeamCity 8.0 in the result.

Ready? Then get the build from the download page.

The forum would be the best place for your feedback and issue tracker - for any bugs you might encounter.

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 EAP build #23833: Branches, Branches, Branches

Our current plan is to release 7.1 within several weeks so this is really close to the release.

Main team efforts are focused around polishing feature branches support, but there are also other improvements that we included at the last minute.
See the release notes and get the build to try now.

We encourage you to try the build on a test server i your environment and see how it works for your settings. If you find any critical issues please file them into the issue tracker.

And we are back to fixing last minute issues now...

TeamCity EAP build #23732: Feature Branches and More

With this new EAP build we are introducing dedicated support for feature branches development practice. The only supported version controls are Git and Mercurial. Support for others might be added too, but not in TeamCity 7.1.


VCS roots has got a new "Branches" field where you can specify patterns for the branches to monitor. The changes are then processed as usual. They are displayed as pending and VCS trigger will trigger builds for them. The builds triggered for non-default branch will  display the branch name. You will be able to filter builds by branches in UI. At the same time, some of the features like notifications and build status work only for the default branch.

If you use Git or Mercurial and use feature branches we would appreciate if you can install a test server and see how this functionality plays for you. We are eagerly awaiting for your feedback for the feature.

For details and other improvements see release notes and full fixed issues list if interested.

Our plans were to release TeamCity 7.1 in about a month and we are reevaluating them now. Options are  to confirm the plans or postpone the release until September.

TeamCity EAP build #23373: NTLM SSO, Artifact Dependencies Changes, Always-Execute Build Steps and More

Last week we have published a new EAP build #23373 which reflects current state of our trunk, TeamCity 7.1 development. Sorry for the late announce here: Adriatic Sea around me last week was not very favorable for following the team's status closely.

As usual, you can get the list of most prominent changes in the change log or browse through the fixed issues list. While we are still in development phase we urge you to check the new features and let us know how well they suit your cases and how would you like to improve them. We still have some time to do some polishing before the release, so your feedback would be quite appropriate at this time.

A usual warning: EAP build might be unstable, so production installation upgrade is not recommended. You can try it as a test server, however. In any case, please create a backup of database and settings before upgrade to be safe if something goes wrong.

BTW, if you use JavaScript and use one of JetBrains IDEs with JavaScript support you might be interesting in a recent post in our official blog on setting up JavaScript inspections in TeamCity. Your comments are welcome!