TeamCity 9.0 (code-named Hajipur) EAP is open

Julia Alexandrova

Greetings, everyone!

For quite some time now, before every new version, we’ve been running a very successful Early Access Program (EAP) which helps us improve TeamCity basing on feedback from our most enthusiastic users. So today we are happy to announce that the Early Access Program for TeamCity 9.0 is now officially open! Traditionally TeamCity versions are code-named after Indian cities, and this one is no exception, so please welcome Hajipur 9.0 EAP1 (build 31423).

TeamCity 9.0 plans

Before I talk about the features of this release, let me briefly outline the main directions for TeamCity 9.0.

The estimated release date for the new version is October 2014, which will probably be corrected as we approach the release.

One of the major directions is the ability to move projects among servers. We are currently working on ensuring safe and foolproof transfer of projects.

Among the priorities of the future version is the functionality allowing TeamCity users to store the project configuration settings in the VCS the same way it is done with the source code.

The advent of the cloud solutions gives one more significant course to our work: our efforts are directed toward cloud integration with VMware Vsphere and Microsoft Azure.

In addition to developing these new features, we are also investing considerable resources into improving TeamCity performance, reliability and ease of use.

Highlights of Hajipur 9.0 EAP1 (build 31423)

This release contains a snapshot of our continuing work on the upcoming release. We’ve been working hard and today we are presenting: two-way synchronization of your project settings with the version control – now you can store the project configuration settings in the VCS the same way it is done with the source code, Build Time Report, Unicode support for MS SQL and Oracle databases used by TeamCity and other features, such as the ability to upload meta-runners, tagging queued and running builds and more. We also introduced some changes aimed at speeding up the backup restore operations as well as clean-up, which is gradually being moved to the background.

We encourage everyone to refer to our release notes for details and, if you want to be a part of the TeamCity development process, download this EAP version and give it a try! We are collecting your feedback, so keep it coming! We are thrilled to hear what you have to say!

Help us make the new TeamCity better and happy building!

Comments below can no longer be edited.

10 Responses to TeamCity 9.0 (code-named Hajipur) EAP is open

  1. Pedro says:

    July 31, 2014

    This is great!, could you guys also include support for AWS Spot Instances? TW-10849

  2. Sergey Pak says:

    July 31, 2014

    This feature is currently out of 9.0 scope. Please vote for the issue, so we can start working on it sooner.

  3. Michael says:

    August 25, 2014

    I’m very much looking forward to seeing how project settings in version control will work.

    In the release notes you state that a known limitation is the storing of the passwords in source control once this feature is enabled. Am I correct n assuming this is just something that’s going on during the CTP and not going to actually be part of the final feature?

    Best regards, Michael

  4. Martin says:

    September 30, 2014

    Hi guys,
    is the latest Artifactory TC plugin supported by TC 9.0?


    • Julia Alexandrova says:

      September 30, 2014

      Martin, the TeamCity Artifactory Plugin is developed by JFrog, so, to avoid any confusion, it is best to consult them on the compatibility questions.

  5. Dmitry says:

    September 30, 2014

    @Michael, we are going to extract password to a separate file which won’t be committed to VCS, but it is not implemented yet.

  6. Mike says:

    October 12, 2014

    I really would like to have the link to the EAP1 release since EAP2 has some errors causing upgrade to terminate. I do not have the EAP1 release anymore. It realy would be great if the previous EAP release would not be deleted or hidden.

  7. Alessandro Bortolussi says:

    November 26, 2014

    Hi, I’ve been using TC 9 EAP 2 for a while.

    There’s a problem with the settings synchronization with Git. Every night Stash is rebooted by operations, and the syncronization is lost by TC, which shows an error. Unfortunately TC doesn’t recover it when Stash is back online. Can you please fix this?


  8. Dmitry says:

    December 1, 2014

    Hi Alessandro,

    we fixed a similar issue in TC 9 EAP 4 (, please upgrade and check if it helps.


Subscribe for updates