TeamCity 2021.2 gets 2FA, further integration and enhanced interface

JetBrains has released TeamCity 2021.2, the latest version of its continuous integration and deployment (CI/CD) server, adding features such as two-factor authentication, closer integration with other platforms such as Perforce and Azure DevOps, and enhancements to the Sakura user interface.

Announced on the JetBrains blog, the newest update to TeamCity builds on security for an organisation’s CI/CD process with support for two-factor authentication. TeamCity administrators can now enable two-factor authentication and require users to enter an additional authentication code to log in. Users need to have a mobile device and an authenticator app to scan a QR code to key in.

This release also brings updates to TeamCity’s integration with Perforce Helix Core and Helix Swarm. With Helix, the Run custom build feature now allows users to run personal builds with changes from a shelved changelist in Perforce. A whole build chain can be triggered on such a changelist, with the user able to see the list of shelved files inside the TeamCity user interface.

TeamCity also has added support for the new Perforce Shelve Trigger, which detects new and modified shelved changelists whose descriptions contain a given keyword and triggers personal builds on them.

With Helix Swarm, JetBrains has extended the Commit Status Publisher build feature by adding the new Perforce Swarm publisher. When the publisher is configured, TeamCity will send information about builds to the Perforce Helix Swarm server, and the respective comments are then added to Swarm reviews on shelved changelists. The VCS labeling build feature also now creates automatic labels in the Helix server, which work as aliases for changelist numbers.

JetBrains has also added integrations into TeamCity for its recently introduced JetBrains Space collaboration platform, such as the new JetBrains Space authentication module, which allows users to log in using their Space account, as is possible with GitHub or GitLab.

With the necessary access rights added to Space, the latest release of TeamCity will also allow users to add VCS roots, create projects, and create build configurations from Space, where previously it was only possible to access repositories and publish the status of your builds.

In response to requests from devs that use TeamCity and Azure DevOps together, JetBrains has integrated the new Azure DevOps OAuth 2.0 authentication module, which allows developers to log in to TeamCity with an Azure DevOps account.

For C# developers, there is a C# Script build runner, which provides a way to write build steps using this language instead of having to use PowerShell. The new build runner is cross-platform, works on any system with Docker, and comes with built-in support for NuGet, according to JetBrains.

TeamCity 2021.2 also features enhancements to the Kotlin DSL, which enables developer to manage CI/CD configurations as code. Developers can configure elements of pipelines that were previously not covered by the Kotlin DSL, such as issue trackers, custom charts, or shared resources.

Finally, this release adds two views from the classic TeamCity user interface that were previously missing from the Sakura user interface: Pending Changes and Change Details. In both environments, usernames display avatars next to them, so users can identify the authors of commits more easily.

TeamCity 2021.2 can be downloaded from the JetBrains website.