What's New in TeamCity 2022.02
Storing Docker images produced by build to public ECR registry
TeamCity can now store Docker images produced by a build to both private and — since this update — public ECR registries.
To be able to use this functionality, you need to add an Amazon ECR connection in Project Settings and choose the ECR Public registry type:
Remember to also enable Docker Support in your builds.
Automatic import of user avatars from external systems
When a user signs in to TeamCity via a third-party account, like GitHub or Bitbucket, for the first time, TeamCity will automatically fetch their avatar from the external system and attach it to their TeamCity user profile. Note that TeamCity will only be able to access avatars of users with verified emails (if you are using GitLab, check that a public email is set in your account).
It is possible to upload a different avatar in the TeamCity user profile settings afterwards.
Getting project SSH keys via UI
You can now copy the public part of an uploaded non-encrypted SSH key from the project settings. To do this, go to Project Settings | SSH keys and click Copy the public key under the key name.
This way, project admins no longer need to ask the system administrator for a public SSH key whenever they need it (for example, to integrate their TeamCity projects with a VCS hosting service) — they can just get it via the TeamCity UI.
Applying action to multiple builds
It is now possible to select multiple builds and apply actions to all of them at once:
Pin/unpin
Tag
Compare with another build
Add a comment
Add to favorites
Remove
On the Overview tab of Build Configuration Home, you can select the required builds with checkboxes that appear when hovering over builds. To apply an action to them, use the respective command of the pop-up context menu. If you need to select a range of builds, press Shift and click build checkboxes at the edges of the range to be selected.
Kotlin DSL update: Import statements include only current DSL version
Since this version, all import statements in a Kotlin DSL code no longer include the DSL version specification. Instead, the version is determined automatically based on the current server's version.
This change affects how a DSL code appears in the View as Code mode in TeamCity and removes irrelevant suggestions when writing import statements manually in an IDE. It concerns only newly created projects — the syntax of existing projects is supported for compatibility.
Perforce integration update: Automatic creation of Helix Swarm test runs and status synchronization with builds
Commit Status Publisher has a new option for sending build status reports to Perforce Helix Swarm — Create Swarm Test. If you enable it, TeamCity will create a test run on the Helix Swarm server and update its status according to the build status in TeamCity.
Other updates
Composite build configurations no longer appear on the Compatible Configurations tab of a build agent's details.
Composite builds are meta-builds designed for aggregating results of builds preceding them in a chain. Technically, they do not need a build agent to run and thus cannot be matched as compatible/incompatible with them. This usability update removes composite build configurations from Compatible lists to help avoid any potential confusions.
Fixed issues
Upgrade notes
Versions 2017.1 and 2017.2 of TeamCity REST API have been unbundled. If you have been using any of these versions in your scripts, consider switching to the latest protocol version as described here. If switching is not an option and this is a breaking change for your setup, please contact us via any convenient feedback channel.
Roadmap
See the TeamCity roadmap to learn about future updates.