TeamCity 2018.2 released: secondary node, GitHub pull requests, improved plugin experience, screenshots in test results, and Kotlin DSL previews
Please welcome TeamCity 2018.2 – this year’s second major release. With this version, outsource collecting VCS changes to a secondary node, build GitHub pull requests, and install plugins without restarting the server. Screenshots in test results, automatic investigation assignments, and multiple NuGet feeds round out the picture.
Here is an overview of the main new features of the release.
Increase scalability with a secondary TeamCity node
The secondary TeamCity node is designed to take the load off the main TeamCity server by taking over the task of collecting and checking for changes from the Version Control Systems. Outsource the collecting of VCS changes to the secondary node to increase the scalability of your whole installation. It is also possible to use the secondary node for a high-availability setup.
Build GitHub pull requests
TeamCity has extended its support for GitHub pull requests. Filter the pull requests by author and limit them to internal or external collaborators, or open them for everyone. There is also the option to filter pull requests by target branch.
Enjoy working with plugins
- Install from the plugin repository. You can now browse and install plugins in TeamCity directly from the JetBrains plugin repository.
- No server restart. Once a plugin is installed from the plugin repository, you no longer need to restart the TeamCity server for it to be applied.
- Hassle-free plugin development. Similarly, when developing a plugin for TeamCity, there is no need to restart the server anymore.
Add screenshots in test results
TeamCity 2018.2 lets you add screenshots and other test data, such as links, artifacts, logs, and numeric values, to the test results. These will be displayed natively in the test details section of the UI.
Preview settings in Kotlin DSL
Unsure how best to describe a setting in the Kotlin DSL format? TeamCity now automatically generates DSL code for all your settings and lets you preview it in the admin UI. Handy for learning DSL format or for just copying parts of DSL to insert into already existing settings.kts file.
Assign investigations automatically
You can now let TeamCity suggest or automatically assign investigations to team members based on a number of heuristics. That way the person who most likely broke a build will receive a notification to investigate the failure.
Multiple NuGet feeds
TeamCity 2018.2 lets you specify multiple NuGet feeds to be used by builds in a project and all its subprojects. It also introduces support for NuGet Server API v3.
There is more to this release! See the detailed description of these and other features in the What’s new section in our documentation.
Also, sign up for our free webinar on January 8, 2019, to see the new features in action.
Subscribe to Blog updates
Thanks, we've got you!
TeamCity Cloud 2023.09 Is Here
TeamCity Cloud 2023.09 comes with enhanced integrations with Perforce and Space, the ability to report statuses of preceding build steps, and other features.
TeamCity Cloud 2023.07: Major Cloud Profile Improvements, Enhanced Space Integration, and More
The new TeamCity Cloud 2023.07 comes with major cloud profile enhancements, improved TeamCity and Space integration, and more. Read on to learn what's new.
TeamCity Cloud 2023.03 Is Here: Build Cache, Running Steps Only for Failed Builds, Sakura UI Improvements, and More
TeamCity Cloud 2023.03 is now available with numerous improvements and new features. Let's take a closer look at what's new.