In TeamCity Cloud 2023.09, we’re introducing the ability to stream files from agents to the log while the build is still running. TeamCity users will also be able to add parameter-based execution conditions thanks to the new ability to report the statuses of preceding build steps.
We’ve also enhanced a number of TeamCity integrations, including Perforce Helix Swarm and Space, among other features.
Let’s take a closer look at what’s new.
Streaming files from agents into the build log while the build is running
Starting from version 2023.09, TeamCity can stream a file on the agent file system into the build log as the log is being updated (i.e., while the build is still running).
You can now send the following service message to start tracking the contents of agent files and streaming the data into the build log:
##teamcity[importData type='streamToBuildLog' filePath='path-to-file' filePattern='pattern' wrapFileContentInBlock='false' charset='UTF-8']
Read more about writing the file into the build log in our documentation.
Reporting statuses of preceding build steps
As of version 2023.09, TeamCity can report the status of the previous build steps in a build configuration.
You can specify IDs for your build steps (similarly to project and configuration IDs). TeamCity will then use these IDs to generate new teamcity.build.step.status.<step_ID> parameters that report the step exit statuses (“success”, “failure”, or “canceled”).
This feature gives you an opportunity to set up custom conditions of any complexity in your build configuration.
2FA: Reducing excessive authorization requests
Imagine there are several authentication modules configured on the TeamCity server: the built-in one allowing users to log in using username/password and an external authentication provider (GitHub, Hub, SAML, etc.)
In the updated version, if users log into TeamCity using credentials of an external 2FA-protected service, TeamCity checks whether the user has already passed the 2-factor authentication via the external authentication provider. If so, TeamCity won’t request additional authentication. This greatly simplifies the login process while still ensuring security.
Currently, the following authentication providers are supported: GitHub, GitLab, and Bitbucket Cloud.
Enhanced integration with Perforce Helix Swarm
In TeamCity Cloud version 2023.09, we have enhanced the Perforce Helix Swarm publisher of the Commit Status Publisher build feature. Instead of creating its own tests, TeamCity can now reuse workflows and tests that already exist in your Swarm setup.
Automatic publishing of build statuses to Space
With version 2023.09, we continue to enhance the native TeamCity and JetBrains Space integration. TeamCity build configurations that target JetBrains Space repositories do not require a configured Commit Status Publisher build feature for posting updates related to builds. If you establish a TeamCity project through a predefined Space connection, build statuses will be posted automatically.
For the full list of the new features, please refer to the What’s New section in our documentation.
Feel free to share your feedback in the comments below or on the forum. We’ll be happy to help.
Happy building!