Features Releases

TeamCity 2019.1: New UI, GitLab Integration, Support for Go, Token-Based Authentication, AWS Spot Fleet Requests

Please welcome TeamCity 2019.1—the first major release of this year! TeamCity 2019.1 provides a redesigned UI, native GitLab integration, and support for GitLab and Bitbucket server pull requests. Also included are token-based authentication, detection and reporting of Go tests, faster build agent upgrades, and AWS Spot Fleet requests.

800x418_Twitter_card_release @2x

Here are the key new features of the release.

New look, new feel, fewer clicks

TeamCity UI is getting a major overhaul, and here’s a first taste of what you’re going to get in this version.

Not only have we improved the look, but we’ve also updated the underlying technology stack so now the UI works as a single-page application, which means you can access parts of it faster and all the changes appear instantly. See the full TeamCity UI roadmap to stay up to date with all the planned changes.

In 2019.1, we are targeting the pages related to working with projects and build configurations.


The new sidebar provides easy access to your builds and projects. The quick search lets you navigate to other build-related pages.
The project overview has been completely reworked and now provides a dashboard-style view over your build configurations.
The reworked Branches tab on the build configuration overview now displays your default branch, increasing the visibility of the most important data.


Full GitLab support out of the box

Using GitLab? TeamCity 2019.1 adds full support for GitLab. You can now set up a GitLab connection and create projects in TeamCity with one click, by simply picking a GitLab project from the list.

We’ve also added support for GitLab merge requests, so you can now set TeamCity up to automatically run the build on each merge request and then automerge it if the build is successful.


Go the distance

The Go language is now supported natively by TeamCity. Add your Go projects and TeamCity will detect and report Go tests, providing rich insights into the test status, its history across the builds and its duration, and will mark unstable tests as flaky.


Token-based authentication

In addition to basic HTTP authentication, TeamCity now supports authentication based on permanent access tokens. With tokens, you don’t need to expose a user login and password in scripts. Tokens are also useful for REST API authentication.

Snapshot dependencies without sources synchronization

You can now set up TeamCity to trigger snapshot dependencies so that it does not synchronize the revisions of code. This is handy when running deployments and lets you promote one of the older builds in the chain using the latest deployment configuration.


AWS Spot Fleet requests

With this more flexible way of creating Spot Instances, you now have more granular control over your Spot Fleet. TeamCity 2019.1 lets you submit and edit the spot fleet configuration file and specify the strategy, set the target capacity, and add tags to your instances. It is a more advanced and cost-effective way of running your builds on AWS.


Processing build lifecycle on a secondary node

The secondary node now has an additional responsibility: processing the build lifecycle. If you turn it on, the secondary node will handle the build-related tasks, such as running and finishing builds, uploading artifacts, and failure conditions processing. This change expands the already broad list of tasks that you can offload from your main server onto a secondary one: collecting changes from agents, serving as a read-only backup node, and now, processing the build lifecycle.


On-demand tools loading

Tools will now only be loaded onto agents on demand. The necessary tools will be loaded only when the first build requiring them appears. This significantly improves the build agent upgrade times and saves you network traffic.

There is more to this release! See the detailed description of these and other features in the What’s new section in our documentation.

Download TeamCity 2019.1

Please check through the upgrade notes before you install the new version, and do not hesitate to report any issues in our tracker or ask questions in the forum.

Comments below can no longer be edited.

8 Responses to TeamCity 2019.1: New UI, GitLab Integration, Support for Go, Token-Based Authentication, AWS Spot Fleet Requests

  1. Avatar

    steve says:

    May 29, 2019

    any documentation from upgrading 2017.3 to 2019.1 ?

    • Avatar

      Yegor Naumov says:

      May 31, 2019

      Hi Steve, TeamCity supports upgrade from any previous version, so nothing special is required for 2019.1. Please see the docs about upgrading TeamCity here: https://www.jetbrains.com/help/teamcity/upgrade.html

      Also, there is an automatic upgrade option available starting from 2017.2 – you can upgrade right from the TeamCity UI.

  2. Avatar

    dario says:

    June 7, 2019

    I can’ switch back to old overview. Haw can I reset this setting?

    • Avatar

      Pavel Sher says:

      June 7, 2019


      It is possible that you experience this problem: https://youtrack.jetbrains.com/issue/TW-60459

      To disable new UI you need to turn off “Use experimental UI” option in your profile.

      BTW, if you have some feedback, why you decided to use classic UI, we’d be glad to hear it.

      • Avatar

        Mirek Svoboda says:

        July 3, 2019

        New UI is far less intuitive than the old one. I have to click much more during my day. similar sad “improvement” happened e.g. to AWS CodeDeploy.

        • Avatar

          Ekaterina Shliakhovetskaja says:

          July 3, 2019

          Hi Mirek,

          I am sorry you have to click more. Would you please share what is inconvenient for you now? I believe we can keep the ‘modernization’ trend and make you feel better 🙂


  3. Avatar

    Maxim Cherednik says:

    June 25, 2019

    Guys, it is a great change, but it is not straightforward what are those charts on the build overview. Some hover info would help.

    • Avatar

      Denis says:

      June 27, 2019

      Hello Maxim,

      thank you for the report.

      We are considering some approaches to solve this problem.
      At first look, the next task (https://youtrack.jetbrains.com/issue/TW-60991) should help in this case.

      If you are interested in, please, vote for the task and feel free to leave any idea you would like to be implemented within the task.

Discover more