What's New in TeamCity 2023.03
New Build Cache Feature
We're expanding the list of build features with Build Cache, the feature that allows you to cache files used by a build configuration (for example, Maven dependencies or NodeJS packages). Cached files can be reused by the same build configuration during subsequent runs or shared with other configurations that belong to the same project. When a build starts, a TeamCity agent downloads the latest cache version to the project's working directory, optimizing and accelerating the build process.
The Sakura UI Improvements
We continue actively developing the Sakura UI to provide feature parity with the classic UI and to support the new features. In this version, we improved the visibility of changes.
The Change Log tab is now available for projects and build configurations.
The Show graph option has been implemented on all pages and tabs related to changes. With this option enabled, the changes are displayed as a graph of commits to the related VCS roots.
Accelerated Artifact Upload
Starting with version 2023.03, TeamCity breaks down large artifact files into chunks and uploads these chunks in parallel. As a result, compared to previous TeamCity versions, the artifacts are faster uploaded to the server and become available sooner.
Run Steps Only for Failed Builds
You can now choose the "Only if build status is failed" execution policy for individual steps. This policy allows you to create steps that will be ignored when your build finishes successfully and executed only when it fails.
Kotlin DSL: Build Failure Conditions on Custom Metrics
You can now use Kotlin DSL to configure a build failure condition on a custom statistic value reported by the build. You do not need to edit the main-config.xml file for this, which means that configuring a build failure condition on a custom metric no longer requires system administrator privileges.
The sample Kotlin DSL code is as follows:
We are working on improving the web UI representation of the build failure condition on custom metrics added via DSL.
Integration with Bitbucket Server and Data Center
In addition to Bitbucket Cloud, TeamCity now supports Bitbucket Server and Data Center. The corresponding option is available in the connection types list, and on the Create Project page.
See the following articles for more information: Configuring Connections | Creating and Editing Projects
Commit Status Publisher: Access Token Authentication to Bitbucket Server
Commit Status Publisher now supports access tokens for authentication to Bitbucket Server. When you select the Access Token authentication type, TeamCity will display a list of configured OAuth connections to Bitbucket Server / Data Center configured in the project and available to all project users. Click the Acquire button to obtain the token for the current user. If you are not signed in to your Bitbucket Server / Data Center account, TeamCity will ask for access to it. After you sign in, you will be able to acquire a token for the required connection. TeamCity will display the information about the user that obtained the token and the connection that provided the token.
Reissuing Refresh Tokens for VCS Roots
For Bitbucket Server, Bitbucket Cloud, and GitLab VCS Roots, you can easily reissue the refresh token used by the VCS root with a token issued for the current user by clicking the Acquire new button. For details, see this section.
Server Health Reports for Archived Projects
You can now generate Server Health reports for archived projects. To do this, select the <Archived Projects> scope.
See the TeamCity roadmap to learn about future updates.
We'd Love to Hear From You
We place a high value on your feedback and encourage you to share your thoughts and suggestions. See this link for more information: Feedback.