TeamCity 2018.1.1 is here

A month has passed since we published TeamCity 2018.1. During this month we tirelessly processed feedback from you fixing the regressions that we accidentally introduced in 2018.1. We’re very grateful to our users who installed version 2018.1 and reported bugs back to us. Your patience and willingness to improve the product are very much appreciated!

2018.1 indeed broke a few things. For instance, a major problem was found in the NuGet feed implementation, some users experienced problems with the “History” builds appearance after the upgrade, the agent side checkout with Git did not work in some cases, etc.

All these problems and many others have been fixed in the current version, 2018.1.1. This build also brings fixes in Kotlin DSL, memory usage optimizations and a few performance fixes. See the list of all fixed issues in our Release notes.

As usual with bugfix releases, TeamCity 2018.1.1 has the same data format as 2018.1 does, making it easier to upgrade/downgrade between these versions.

If you’re using a recent version of TeamCity, consider using our automatic upgrade. In other cases, you can download the new version from the website or pull the new version of the TeamCity docker image.

Your feedback is welcome in our forum or tracker.

Happy building!

This entry was posted in Bugfix, Release. Bookmark the permalink.

2 Responses to TeamCity 2018.1.1 is here

  1. Boris says:

    Hello Pavel,

    I am developing and testing a custom TeamCity plugin on TC 2018.1.2 (build 58537)

    It’s a simple plugin with server/common/agent parts built based on Maven template. The new build step appears in the build configuration edit mode, but Build Runner does not appear on the Agent. I posted a question on support forum, but it was not answered:

    https://teamcity-support.jetbrains.com/hc/en-us/community/posts/360000895640-Build-runner-is-not-available-on-agent-in-custom-plugin

    Can you please assist how can I troubleshoot this?

Comments are closed.