Thanks to Matrix builds in TeamCity, you can define a combination of parameters and corresponding values to create a matrix of builds. Each combination of parameter values generates a unique build. The matrix build is then made up of several multiple builds running in parallel.

Matrix builds are especially useful when testing software across different configurations, such as operating systems or browser versions.

Read more about matrix builds in our documentation.

In CI/CD, using single-use build agents is considered the best and most secure practice. But best practices don’t come without challenges.

Every time you run a build on a single-use build agent, heavy or multiple libraries need to be downloaded from the internet in order for the build to be executed. This causes slow build times and delays in starting the build.

No more!

Build caches help you optimize your CI/CD build time by downloading the files that your project depends on and then reusing them again within the project.

Learn more about Build Caches in our documentation.

With the 2023.11 release, we’ve completely rethought our approach to setting cloud profiles and images. The new UI guides you through the process, suggesting relevant setting options.

You can now benefit from using EC2 Mac instances, running AWS EC2 spot instance build agents with a spot placement score, and much more.

The S3 plugin also got a new intuitive and streamlined UI designed with both Amazon S3 buckets and S3-compatible storages in mind.

Learn more in our documentation.

TeamCity offers seamless integrations with Git hosting platforms, including GitHub, GitLab, Bitbucket (both Cloud and Data Center), and Azure DevOps.

In 2023.05, we introduced a new type of connection to GitHub. Instead of utilizing the traditional OAuth-based access to repositories, you can use GitHub Apps instead.

Starting from version 2023.11, you can establish these connections more efficiently, eliminating the need for manual configuration and registration of new apps in GitHub.

On the authentication side, you can now also issue impersonal refreshable access tokens for GitHub App connections on the Commit Status Publisher, Pull Requests build features, and GitHub Issue Tracker settings pages.

Starting from version 2023.11, you can configure TeamCity to ignore draft merge requests in the Pull Requests build feature for GitLab.

Commit Status Publishers and Pull Requests that target GitLab repositories can now use refreshable OAuth tokens to pass the authentication.

Commit Status Publishers and Pull Requests that target GitLab repositories can now use refreshable application tokens to pass the authentication.

TeamCity now supports refreshable OAuth tokens for Commit Status Publisher and Pull Requests build features for Azure DevOps.

Learn more in our documentation.

With this release, we’re enhancing Bitbucket authentication in several ways.

In addition to app passwords and VCS Root credential authentication types, TeamCity also supports refreshable and permanent access tokens as an authentication method for the Pull Request Build Feature for Bitbucket Cloud.

The Pull Requests feature can now use refreshable OAuth tokens to access repositories on Bitbucket Server / Data Center.

Learn more from our documentation.

We’ve also improved the existing Swarm and TeamCity integration. The integration allows you to use TeamCity build statuses in Swarm and navigate from the TeamCity UI to the Swarm interface.

Starting from version 2023.11, the TeamCity Perforce Helix Swarm publisher for the Commit Status Publisher build feature can be integrated with custom workflows that already exist in your Swarm setup. In addition, the Commit Status Publisher no longer requires the credentials of users with administrator access.

Now, it’s possible to set up the integration without using Swarm administration-level credentials in TeamCity. The updated integration also allows including gates based on TeamCity checks into custom workflows.

Learn more in our documentation.

You can now mark certain agent pools as favorites and access them from a unified place. This comes in handy when you need to access the agent pools that you are responsible for.

Agent terminal is a unique TeamCity feature that provides a convenient and quick way to get direct access to an agent machine by opening a remote terminal directly from the TeamCity UI. It is supported on Linux, Windows (with PowerShell), and macOS.

Starting from version 2023.11, you don’t have to switch tabs in order to open agent terminals – they open on the same page in the TeamCity UI.

Developers have every right to feel comfortable while using their daily tools. This is why we’ve developed one of the most upvoted features in TeamCity’s history: the dark theme.

The dark theme can help reduce eye strain and eliminate visual distractions. Additionally, some users find it more aesthetically pleasing.

TeamCity's dark theme is available for both the Classic and Sakura UIs. In addition to the Light and Dark options, you can also choose System theme which will automatically match your OS settings.

In TeamCity 2023.05, you can now open remote terminals to agent machines directly from the TeamCity UI in order to easily view agent logs, check installed software, and debug specific agent issues.

This new feature is particularly useful when troubleshooting issues on an agent, as remote terminals eliminate the need to maintain SSH keys for connecting to agents. It is supported on Mac, Linux, and Windows (with PowerShell).

With this release, we’re also implementing an improved request distribution logic that efficiently distributes the load between the main and secondary nodes.

To enhance TeamCity's scalability, nodes are now completely interchangeable. All nodes within the TeamCity network can contribute to balancing user requests, thus enabling a more even distribution of the workload generated by users of the web UI across all nodes.

In the 2023.05 version, TeamCity users are no longer constrained to a single node for VCS repositories polling duties. The latest release permits this function to be delegated across multiple nodes, resulting in a more even workload distribution, faster identification of new commits, and faster build initiation.

By leveraging this feature improvement, users can streamline their build, test, and deployment processes, enhancing overall efficiency, reducing delays, and boosting productivity.

At TeamCity, ensuring robust security is our top priority. To reinforce the product's ability to resist data breaches and potential business disruptions, we have incorporated the following features.

TeamCity now includes integration with Let's Encrypt, a certificate authority that offers free and automated digital certificates to facilitate HTTPS on websites. By contacting Let's Encrypt, TeamCity can automatically obtain and install a valid certificate that will subsequently be updated without any user intervention.

In previous versions, enabling the mandatory two-factor authentication mode affected the entire server. However, with this latest release, it is now possible to form custom user groups that will require the use of 2FA even if the global mode is set to Optional.

TeamCity users can already configure email and Slack notifications for specific events. Version 2023.05 makes this feature even better, allowing you to send Slack messages and email notifications using service messages.

For the full list of new features, please visit our What’s New page in the documentation.

As always, we’re looking forward to your feedback! Feel free to submit a request via the support form.

Sakura /sa.ku.ʁa/, or cherry blossom, symbolizes the time of renewal and optimism – and we believe this perfectly describes our feelings as we make the Sakura UI default in TeamCity 2022.10.

The Sakura UI is modern, beautiful and fast. Built with accessibility in mind, it has feature parity with the classic UI, and also brings many new unique capabilities. We’ve been working on the Sakura UI for over four years, and we made sure to make it perfect down to the smallest detail. We had the unique opportunity to test it against thousands of internal and external projects including such giants as IntelliJ IDEA and Kotlin. We believe that you will love it too!

We understand that some of our users may be attached to the old user interface, and for a limited time we will keep it available for them. However, in one of the next versions, we will be deprecating it in favor of the Sakura UI, so if you think that we have missed something, please create an issue in YouTrack.

We have implemented a new AWS credentials management system that issues temporary, short-lived AWS keys and exposes them in a safe way for your builds.

If you've ever needed to debug a problem in a CI/CD pipeline that was executed on a cloud instance, you know that it can be tricky. Not only does it require time and effort to identify and spin up the right build agent, but you also need to make sure that it doesn’t launch new builds in the middle of the process.

This is where maintenance mode comes in. In this mode, TeamCity does not automatically terminate cloud agents after the build is finished, and they don’t get allocated for running new builds, allowing you to do the troubleshooting.

Starting with TeamCity 2022.10, secondary nodes of TeamCity can start and stop cloud instances, providing uninterrupted operation of cloud-based CI during maintenance of a primary server.

TeamCity 2022.10 comes with two improvements related to the integration with Perforce tools:

• Perforce Shelve Trigger now understands when a shelved changelist is related to a non-default stream and allows the build to be run on it.
• TeamCity now detects changelists that have reviews in Perforce Helix Swarm and adds links to the respective review and change pages in Build Overview and Changes pages, respectively.

TeamCity 2022.10 now uses short-lived OAuth tokens when working with GitLab, Bitbucket Cloud, and Azure DevOps, allowing you to create VCS roots without having to manually generate access tokens for these services.

To support more workflows and make the experience with TeamCity smoother, we now support authentication using Google accounts. When logging in with Google, TeamCity will instantly match the Google email with an existing TeamCity user, and log them in without having to enter a password. It can also automatically create new profiles when new members join your team, provided that their email addresses belong to one of the domain names you specified.

The Free Disk Space build feature now keeps track of the size of artifacts and automatically calculates the disk space required for resolving artifact dependencies. This makes the use of the build feature more straightforward, as you no longer have to know the size of the artifacts downloaded during the build, and the only thing you need to specify is the amount of disk space required for the build process itself.

Starting with TeamCity 2022.10, you can promote personal builds. Builds that are triggered after the promotion also become personal builds.

TeamCity has always had powerful integration with Amazon EC2 and Amazon S3 that allowed you to freely scale your build infrastructure, regardless of the size and complexity of your projects. Version 2022.04 allows you to not only store new build artifacts in Amazon S3, but also move existing artifacts from TeamCity’s local storage to Amazon S3. This is particularly useful for teams who are just starting their migration from a self-hosted setup to a cloud platform and want to take full advantage from the outset.

Storing CI/CD configuration with your project’s codebase is the best way to ensure that it can always be built, tested and deployed. To provide more flexibility when building software in the cloud, TeamCity 2022.04 extends the Kotlin DSL, giving every project the opportunity to have its own Cloud Profile configuration.

We’re continuing to improve the integration with JetBrains Space, adding in support for merge requests. When building an MR, TeamCity will now publish the status to the respective merge request timeline in Space.

We have enriched the list of supported issue trackers by adding GitLab. This works just as you’d expect: when a commit message mentions an issue ID, TeamCity automatically adds a link to the respective issue in GitLab and displays information about it.

Previously, the Commit Status Publisher build feature would not send information to the version control system until TeamCity actually started the build, which was prone to occur long after the commit had been made. Starting with the new version, TeamCity updates the commit status immediately after adding the respective build to the queue, providing you with the most up-to-date information. This feature works with all supported VCS services including GitHub, GitLab, Space, Bitbucket and Azure DevOps.

Although TeamCity has not been affected by the Log4Shell vulnerability (CVE-2021-44228), some security scanners wrongly reported it as vulnerable without checking the exact version number of the Log4J framework used in the product. To avoid false-positive scanner reports, we have upgraded Log4J to the latest version.

Similarly to Log4Shell, the Spring4Shell vulnerability (CVE-2022-22965) does not affect TeamCity. However, to avoid false-positive reports from security scanners, we have upgraded the Spring Framework used in TeamCity to the latest version.

Our new Sakura UI is getting closer and closer to feature parity with the classic TeamCity UI. In version 2022.04, we have reimplemented the Agent Pools and Changes pages and vastly improved the overall performance of the new UI. Now we are just a few steps away from making it a default option – something we plan to do in TeamCity 2022.10. Stay tuned!