What's New in TeamCity 2024.07

Experience seamless license management with our newest JetBrains Account integration. Log into the JetBrains Account from TeamCity and choose a server license to activate. Once connected, TeamCity will automatically receive updates for all server and agent licenses, meaning you will no longer need to manually enter your license codes for any additional agents or server subscription updates.

The new mechanism does not impact existing licensing or purchase policies and is entirely free, regardless of your server license type (including free-tier Professional servers). It benefits all TeamCity users by linking your server instance to the JetBrains account, enabling server administrators to receive timely email notifications about critical security updates.

Learn more: Manage TeamCity Licenses.

When you enable synchronization on the Versioned Settings page in your project settings, you can now specify a custom location for your remotely stored Kotlin DSL scripts and XML settings.

This flexibility is especially beneficial for teams working with monorepos. It allows multiple standalone TeamCity projects to target the same repositories without conflicts, by storing project settings in different custom directories instead of the default .teamcity folder.

Additionally, this feature enables you to organize the versioned settings of all your projects in a single repository. This streamlined approach simplifies DSL script maintenance and enhances security by keeping configuration files separate from your main codebase.

Learn more: Storing Project Settings in Version Control Systems

Starting with this version you can store the contents of your server's <TeamCity Data Directory>/config directory in an external repository. This setup allows you to view and investigate the complete history of server edits, and easily restore these configuration files should they ever become corrupted.

Learn more: Upload Configuration Files to a Version Control

When you create a new project from an SSH URL, TeamCity shows a list of available SSH keys. Starting from this version, you can upload new keys directly from this page.

This minor enhancement streamlines the workflow by eliminating the need to upload keys in advance from the SSH Keys page.

Learn more: Upload SSH Keys to TeamCity Server

We have overhauled the Problems tab of the Project Home Page to simplify the user experience and facilitate build failure investigation and resolution workflows.

In futher release cycles, we expect to update other UI elements related to browsing, investigating, muting, and fixing build problems.

Learn more: Working with Build and Test Failures

• The list of statistic values reported by TeamCity now includes the AllTestsDuration value.

• The database connection setup wizard that pops up during the first TeamCity server launch now installs the following JDBC drivers depending on the selected database type:

  • MySQL database file: mysql-connector-j-8.3.0.jar

  • MS SQL server: mssql-jdbc-12.6.0.jre8.jar and sqlserver12-win-auth.jar for authentification.

  • PostgreSQL: postgresql-42.7.1.jar

• The backslash character (\) is now the default escape symbol that allows you to use special characters in feature branch specifications. This symbol was commonly recommended as an escape symbol in TeamCity documentation and support tickets, and you might already have branch specifications that look like the following:

  #! escape: \
  +:release-\(7.1\)

  This first line is no longer required and can be safely removed, but your existing specifications will remain valid even if you don't.

• TeamCity now supports Perforce depots mapped to multiple workplace locations (the ditto mapping).

• The VCS Labeling build feature now allows you to specify a string that should be written to the description field of Perforce labels.

  

• TeamCity metrics set now includes four more experimental metrics that allow you to measure the number of tasks that carry out version settings synchronization.

  • executors_versionedSettingsUpdate_activeTasks

  • executors_versionedSettingsUpdate_completedTasks

  • executors_versionedSettingsUpdate_poolSize

  • executors_versionedSettingsUpdate_queuedTasks

  In addition, the new build_queue_incompatible metric allows you to track the number of builds that are not compatible with any of the currently available TeamCity agents (including cloud existing cloud profiles).

Before upgrading, we highly recommend reading about important changes in version 2024.07 compared to 2023.03.

See the TeamCity 2024.07 release notes article for the summary of implemented features and fixed issues.

See the TeamCity roadmap to learn about future updates.

We place a high value on your feedback and encourage you to share your thoughts and suggestions. See this link for more information: Feedback.