On this page:
Conditional build steps
Now, you get granular control over build steps with the new execution conditions.
When editing a build step, click Add parameter condition and specify a logical condition for any build parameter provided by the TeamCity server.
Similarly to agent compatibility requirements, TeamCity will suggest available parameters and values. A wide set of logical conditions is available.
A build step will be executed only if all its execution conditions are satisfied in the current build run.
This flexible approach gives multiple new opportunities:
- Run a given build step only for a particular build branch
- Run a build step only for personal or non-personal builds
- Run a build step only if a custom parameter, provided via the Custom run dialog, is set
- and more
Displaying TeamCity build information in Jira Cloud
TeamCity can already integrate with Jira to give quick access to Jira tasks, mentioned in the builds' commits. Now, it can also report build statuses directly to Jira Cloud in real time.
To be able to use this feature:
- Add a Client ID and Server secret to your existing Jira Cloud issue tracker connection.
- Add the Jira cloud integration build feature to your build configuration. You will need to select the created connection, an environment type (for example, testing or production), and come up with a unique environment name.
If you mention a Jira task ID in the commit message in VCS, TeamCity will detect this message during the build containing this commit and send information about the build to Jira.
The build status is displayed in the Jira task details:
Since this version, Slack integration is built into TeamCity. It allows receiving notifications with specific build events and details in private messages or via a Slack channel.
To set up Slack notifications, you will require to create a Slack app. Then, add a Slack connection in Project Settings | Connections and enter the required app’s parameters:
Two notifying options are available:
Individual notifications configured in a user profile, like any other notifications in TeamCity.
To create an individual notification rule, go to My Settings & Tools | Notification Rules | Slack Notifier, select the Slack connection for a required project, sign in as a Slack user, and select events to send notifications about:
Notifications on a build configuration level, which is a new way to configure notifications about a single build configuration (or an entire project in a template). With this feature, you can send notifications to a specific Slack user or channel, based on their ID.
To configure a rule for a build configuration, go to Build Configuration Settings | Build Features and add the Notifications feature with the Slack type.
Improvements for secondary nodes
With each release, we come closer to providing a full-value TeamCity experience on secondary nodes. This EAP introduces the following functionality:
- Automatic update via web UI, similarly to the main server autoupdate
- Agent-related user actions on secondary nodes
Experimental UI: Reordering projects in sidebar
One of the most requested features, missing in the experimental UI, was the ability to reorder projects. With this EAP, we address your feedback by adding this functionality to the experimental UI sidebar.
To start customizing the projects sidebar, click in its upper-right corner. You can move a project or build configuration in the list via a keyboard or using the arrow UI button. You can also mark/clear projects as favorite directly in this configuration window.
- TeamCity uses the BCrypt algorithm to make user password storage safer.
- The Project Settings | Build Schedule tab now has an alternative filter option: hide triggers with the enabled "Trigger only if there are pending changes" option. This helps if you need to quickly find all triggers where this option is disabled to investigate the builds’ behavior.
See all fixed issues.