TeamCity 2018.1.2 is released

Julia Alexandrova

We are happy to announce TeamCity 2018.1.2, the bugfix update containing over 100 fixed issues in various areas of TeamCity. The changes are mostly related to

  • Kotlin DSL
  • Performance
  • Security (several new XSS’s were fixed)

Besides, starting from this version TeamCity supports several read-only nodes running simultaneously.

The complete list of fixes is available in our release notes.

Check the Upgrade Notes before you install the new version and do not hesitate to upgrade: version 2018.1.2 has the same data format as all 2018.1.x builds do and makes it possible to upgrade/downgrade between these versions.

TeamCity offers several upgrade options:

Your feedback is welcome in our forum or tracker.

Happy building!

Comments below can no longer be edited.

10 Responses to TeamCity 2018.1.2 is released

  1. Halstein Tonheim says:

    August 31, 2018

    Warning to users:
    Stay away, this versions seems to completetely broken.
    1. It is VERY slow. Allot slower than 2018.1.1.
    2. Seems like some services are broken.
    a. Version numbers are no longer displayed on builds (just says “Not defined”)
    b. Project list is empty (just displays “Failed with error 500”)
    c. Build progress bar is not displayed at all.

    This was the issues at first glance. I am sure there are allot more wrong with it.

    I will be trying a rollback and hopefully 2018.1.1. Will get everything working again.

    Note: We upgraded using the upgrade functionality in TeamCity itself.

    • Pavel Sher says:

      August 31, 2018

      Please create a bug report in our tracker with all of the logs attached.

      • Pavel Sher says:

        August 31, 2018

        So far we can’t reproduce any of the mentioned problems.

        TeamCity 2018.1.2 is installed not only on but also internally in JetBrains and builds all our products. So far it works just fine.

        We doubt the problem is widespread, but there can be some local issues caused by specific environment. We’ll look into these problems once we get a chance to see logs.

      • Halstein Tonheim says:

        August 31, 2018


        The teamcity-server.log clearly show things going very wrong after the update. Around 2018-08-31 13:37:50 the errors start streaming in: “Unexpected response while executing internal Rest API request”.

        The log file starts on 2018-08-24, but half of it is between 2018-08-31 13:37:50 and [2018-08-31 15:14:59, which is when we downgraded back to 2018.1.1.

    • Halstein Tonheim says:

      September 1, 2018

      The bug is in the TcWebHooks plugin (1.1-alpha17.235.354, latest as of writing). If this plugin is installed on TeamCity 2018.1.2 the UI bugs out completely. We uninstalled this plugin and the problem cleared up completely. Also, the plugin has now issue with TeamCity 2018.1.1.

      If you are depending on this plugin, don’t upgrade to 2018.1.2 until the plugin has a new compatible version.

      • Brett Green says:

        September 11, 2018

        There is a patch release for this in tcWebHooks but I am now reluctant to update TeamCity because of my reliance on it.

        This just makes me wish that there was native support in TeamCity for Slack messages (like a LOT of people use Slack) and/or some kind of native webhook support. The plugins available to help me do slack notifications have not (a) really been what I needed and/or (b) been very well maintained. tcWebHooks is the right approach I believe (open-ended webhook support), but has some issues with competing JAR files and some unfinished features that require modifying XML on the server itself.

        Generalized webhook support would go a long way to making TC more integratable with the rest of the tools teams use.

  2. Jacob Johnston says:

    September 10, 2018

    For anyone else that may be looking – I was having the same issue with TcWebHooks. The author of the plugin published a fix available here:

  3. David says:

    October 10, 2018

    We upgraded to 2018.1.2 on Monday, and to 2018.3 this morning hoping to fix the broken UI since 2018.1.2 upgrade.
    Please see image for example of broken UI. The UI is missing many components (due to failed bindings i guess) including:
    – missing build/branch info
    – missing artifact links

    Has anyone experienced this or have advice?

    • Ekaterina Shliakhovetskaja says:

      October 10, 2018

      I am very sorry about this. I suppose it caused by network/proxy settings. May I ask you to create a bug report in our issue tracker so we can discuss how to figure out what’s exactly and how to manage this? We will add a clear message to simply the diagnostic for such situation in future versions.
      Thank you!
      Best regards,


Subscribe for updates