TeamCity 2017.2 is released!

We are thrilled to announce that TeamCity 2017.2 has been released today!

First of all, we’d like to thank all our users who helped us make the product better:
it really means a lot to know that you are willing to take time and report your success or problems, that you venture to try out our pre-release versions, that you are as excited about the new release as we are. We, the TeamCity team, really appreciate this.

650x170_newsletterTC_2017_2_2@2x

Now let’s talk about the TeamCity licensing news: the TeamCity Professional license increased the number of build configurations, and instead of the 20 you are now entitled to 100 build configurations with our free version!

Why we decided to increase it? We believe that as projects and teams grow, they can get more and more benefit from TeamCity and take advantage of the features which are visible on larger-scale installations. For instance, with a limit of 20 build configurations, there is a little chance you’ll be able to put to full use such features as snapshot dependencies, Kotlin DSL, templates or even projects hierarchy. Not to mention that the modern trend towards microservices architectures also requires a larger number of different build configurations.

Next, this release is packed with new features; most of them have been already announced in our early access program for TeamCity 2017.2, so here is the summary:

  • The built-in TeamСity-Docker integration is now available for agents on Mac, Linux, and Windows. The integration provides a number of features to facilitate working with Docker under TeamCity.
  • Out-of-the-box support for .NET CLI: you can now build, test, and deploy .NET Core projects
  • Aggregated results from several build configurations can be now obtained using Composite builds
  • Deployment build configurations make it easier to deploy and redeploy the results of the builds such configurations depend on
  • Easy TeamCity server upgrade with the new automatic update option
  • and much more, including the improved UI.

The detailed description is available in the What’s New.

Download the brand new TeamCity 2017.2 and check the Upgrade Notes before you install the new version!

Don’t have the time and resources to set up a test server? Test drive the latest version of TeamCity in the cloud.

We always carefully consider your feedback and you are most welcome to use our forum or tracker.

Happy developing and building!

This entry was posted in Features, News & Events, Release. Bookmark the permalink.

6 Responses to TeamCity 2017.2 is released!

  1. Jim Kosche says:

    Hi, just upgraded to: TeamCity Enterprise 2017.2 (build 50574)

    Now when clicking on any of the links in the drop-down menu for a build configuration (like Overview, History, Statistics, etc) a HTTP400 webpage not found error results. The Edit Settings link appears to be the only link that works.

    Is this a known issue? Is there any easy way to fix this?

    Thank you.

  2. Sergey Limonov says:

    Hi,

    It seems that docker image is not upgraded yet. When you are going to upgrade it?

    Thanks

    • Pavel Sher says:

      We updated all images in https://hub.docker.com/ the same day when 2017.2 was released. What particular docker image is not updated?

      • Sergey Limonov says:

        This one https://hub.docker.com/r/jetbrains/teamcity-server/ was last pushed 23 days ago when I read this blog (Dec 18, 2017). Now I see it was last pushed 3 days ago. I have following docker-compose.yml file.
        version: ‘2’

        services:
        db:
        image: postgres:latest
        container_name: jetbrains-teamcity-db
        restart: always
        # ports:
        # – 5432:5432
        environment:
        POSTGRES_PASSWORD: dbhnefkbpfwbz
        volumes:
        – ./db:/var/lib/postgresql/data:Z
        – ./conf/init-user-db.sh:/docker-entrypoint-initdb.d/init-user-db.sh:ro

        teamcity:
        image: jetbrains/teamcity-server:latest
        container_name: jetbrains-teamcity
        restart: always
        ports:
        – 8111:8111
        volumes:
        – ./data:/data/teamcity_server/datadir
        – ./logs:/opt/teamcity/logs
        links:
        – db
        environment:
        TEAMCITY_SERVER_MEM_OPTS: -Xmx1024m
        But when I use “docker-compose up” command I see that it was not updated to 2017.2 version.

        [2017-12-23 12:30:59,895] INFO – jetbrains.buildServer.STARTUP – Starting TeamCity server
        [2017-12-23 12:31:00,856] INFO – jetbrains.buildServer.STARTUP – TeamCity version: 2017.1.5 (build 47175), data format version 812
        [2017-12-23 12:31:00,863] INFO – jetbrains.buildServer.STARTUP – OS: Linux, version 3.10.0-693.5.2.el7.x86_64, amd64, Current user: root, Time zone: UTC

        May be I’m doing something wrong?

        • Sergey Limonov says:

          I could update it only after I have changed image reference from
          image: jetbrains/teamcity-server:latest
          to
          image: jetbrains/teamcity-server:2017.2.1
          If I try to revert this change after upgrading image and container it tries to back to the image with version 2017.1.5.

          May be tag “latest” still points to image with version 2017.1.5 ?

Leave a Reply

Your email address will not be published. Required fields are marked *