What's New in TeamCity 2023.11

In TeamCity, you can leverage build parameters to replace raw values across build scripts, configuration/project settings, command-line arguments, and so on. Normally, each a parameter stores only one value. Starting with version 2023.11, you can add the Matrix Build feature to your configurations to specify a range of possible parameter values. When running such a configuration, TeamCity will spawn multiple builds to automatically cycle through these values.

Adding multiple parameters, each with its own set of values, forms a matrix. TeamCity will run a build for each cell of this matrix, and report the results to the Overview page that allows you to identify at a glance which parameter/value combinations are failing.

The Matrix Build feature offers multiple pre-configured options that allow you to quickly set up your build configuration so that it runs in environments that differ by the installed operating systems, default Java versions, and architectures.

Learn more: Matrix Build.

• Build agents now report the DotNetWorkloads_<version> parameter that returns all .NET workloads installed on the agent machine. Learn more: Parameters Reported by Agent.

• The .NET runner now provides the Excluded test assemblies setting for the vstest command. This field allows you to specify paths to files the command should ignore.

  

• If your builds run a large amount of parallel tests in each batch, TeamCity can automatically switch to an alternative test filtering mode that reduces potential performance issues. See this article for more information: Alternative Test Filtering for .NET.

You can now set a specific date and time when a build should run. To do this, invoke the Run Custom Build dialog and use settings from the new Date section.

Learn more: Run Custom Build.

The new Build Cache feature allows configurations to cache files required by builds (for instance, downloaded npm packages) and reuse them in consecutive builds. This technique assists build agents in offloading excessive operations and can significantly speed up your building routines.

In addition to sharing caches with its own future builds, a configuration that caches files can pass them to other build configurations within the same project.

Learn more: Build Cache.

Starting with version 2023.11, you can build distributions of TeamCity agents bundled with custom JDKs. These distributions allow you to install both an agent and a JDK it requires to operate in one go.

To create a custom agent distribution, navigate to Administration | Agent JDKs and add a new JDK option (you will need to specify the platform, the architecture, and a link for TeamCity to download this specific JDK).

When a new option is added, TeamCity will start building your custom agent distribution. You can download custom agent+JDK bundles by clicking Install agent | Full distributions on the Agents | Overview page.

Learn more: Install TeamCity Agent.

Starting from this version, TeamCity can load custom snapshot dependencies, VCS roots and checkout rules from settings stored in a version control system. As a result, you now have even more flexibility to edit versioned settings and create custom branches with settings that significantly differ from those in default/stable branches.

When detecting these previously ignored settings, TeamCity dynamically creates required hidden entities (such as virtual build configurations) that are in effect only for the current build and remain hidden for other revisions/branches that use different settings.

To enable the updated behavior, tick the Apply changes in snapshot dependencies and version control settings option on your project's Versioned Settings page.

Learn more: Apply Changes in Snapshot Dependencies and Version Control Settings.

When you run a build configurations that employs the Parallel Tests build feature, TeamCity splits a build into batches interconnected in an automatically generated chain. In previous version, artifacts produced during such builds were published in these individual batch builds, while a parent build had none.

As a workaround, you could switch to the Dependencies tab when viewing completed configuration builds.

Starting with this version, artifacts produced by batch builds are aggregated in the Artifacts tab of a main build. You can also use the teamcity.build.parallelTests.currentBatch parameter to arrange artifacts produced by batch builds into different directories.

Learn more: Publish Artifacts Produced By Batch Builds.

Starting with version 2023.11, you can specify IDs for your steps (similarly to project and configuration IDs).

TeamCity uses these IDs to generate new teamcity.build.step.status.<step_ID> parameters that report the step exit statuses ("success", "failure", or "cancelled").

You can use these values to perform custom actions depending on the statuses of previous steps. For example, you can craft custom step execution conditions.

Learn more: Step Status Parameters.

The Inspections (ReSharper) runner now features the R# CLT Plugins field that allows you to add your favorite ReSharper plugins (such as StyleCop, CleanCode, or Unity Support) downloaded from JetBrains Marketplace or installed from a local storage.

Learn more: JetBrains ReSharper Command Line Tools Settings.

Added the new service message that allows you to track the contents of the given file and echo new lines to the build log.

Learn more: Writing the File into the Build Log.

• We have reworked the agent Parameters tab. You can navigate to this tab when viewing any TeamCity agent to instantly check this agent's configuration and environment paramters and system properties.

  

• You can now bookmark required agent pools to easily access them from the top of the agents and pools list.

• The Dependencies Tab now displays a find panel that allows you to search for specific dependent builds by configuration names.

• The Interactive Agent Terminal introduced in version 2023.05 now opens in a panel docked to the bottom of an agent details or build results page. You can move it to a separate browser tab by clicking Open in a separate tab.

  

• Performance Monitor now shows absolute values of the consumed/total agent memory.

• You can now switch Build Log timestamps from absolute values to relative to quickly analyze how long it took the build to reach a specific stage.

  

• You can now view and copy connection IDs from the Connection pages in TeamCity UI. This minor enhancement facilitates writing Kotlin DSL code for objects that utilize connections: AWS Credentials features, Docker Support, S3 artifact storages, AWS connections that use other connections, and so on.

  

• Cloud images' Build History tab now displays a search box that allows you to find all builds of a specific cloud agent, even if this instance is no longer available.

  

• The navigation bar now paints the changes indicator bold for favorite projects with changes from the current TeamCity user.

  

• The DslContext object now exposes a string serverUrl property that allows you to get the URL of a TeamCity server in Kotlin DSL code.

• TeamCity distributes agents more effectively and processes large build chains with failing builds faster. Starting with version 2023.11, dependent builds whose "On failed dependency" condition is "Make build failed to start" no longer wait for an available agent when their dependencies fail or are canceled. Instead, the dependent build's status changes to "Failed to start" as soon as possible, and TeamCity proceeds to the next build in the chain.

• The Commit Status Publisher build feature now correctly publishes build statuses for configurations that target refs/(merge-requests/*)/head branches of GitLab repositories (the "merge result" branches). Previously, running TeamCity builds for merge result revisions caused the Publisher to encounter HTTP 404 errors.

• If users log into TeamCity using credentials of an external 2FA-protected service, TeamCity does not send additional 2FA requests. Learn more: Reduce Excessive Authorization Requests.

• You can now add the dateFormat=<value> parameter to URLs used by your log analysis tools to retrieve build logs. Learn more: Modify the DateTime Pattern.

• In addition to builds_queued, builds_started, builds_running and builds_queued metrics, TeamCity now reports an experimental builds_detached metric that allows you to view the number of builds detached from their agents.

Before upgrading, we highly recommend reading about important changes in version 2023.11 compared to 2023.05.4.

See the TeamCity 2023.11 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.