What's New in TeamCity 2025.07
UI Improvements
We remain committed to delivering a modern, intuitive TeamCity experience for all users, whether you prefer pipelines or classic build chains for your CI/CD workflows. This update brings several UI improvements, including:
A redesigned navigation sidebar with a + button for quickly adding subprojects, configurations, and pipelines. You can also set the panel to auto-hide to maximize workspace.
A new What’s New widget to keep you informed about major updates in each release.
An ability to open build logs in full-screen mode.
Public Marketplace Recipes
In 2025.03, we announced a shift from meta-runners to recipes: lightweight, YAML-based custom steps available on JetBrains Marketplace. At the moment, the Marketplace offers more than a dozen of JetBrains-made recipes that automate tasks like pinning builds, downloading artifacts, and updating build statuses.
Starting with this release, third-party recipes are also supported. Browse community-made options, inspect their source code to view implementation details, upload your own recipes to Marketplace, and expand TeamCity’s extensive arsenal of build steps with custom tools.
The Recipes project settings page now displays a comprehensive summary of both private and public recipes available for this project and its children. For public recipes, TeamCity collects recipe data from the Marketplace and shows warnings when a recipe is outdated or taken down.
Learn more: Working with Recipes
Perforce Integration Enhancements
You can now add multiple Perforce Shelve triggers to your configurations. to a configuration. Previously, adding one Shelve trigger locked you out of adding more via the TeamCity UI.
We have implemented multiple new options that allow you to set up periodic workspace clean-ups. See the Workspace Deletion article for more information.
Kubernetes Executor Updates
Introduced a few releases ago, Kubernetes executor leverages your existing Kubernetes clusters by turning them into independent orchestrators for TeamCity builds. Unlike with regular cloud agents that are fully managed by TeamCity, this integration allows the server to offload the build queue to a k8s cluster, granting the later full control over pod lifecycle.
TeamCity 2025.07 introduces a range of Kubernetes executor updates:
Executors are now natively integrated into TeamCity default prioritization mechanism. When a build is queued, TeamCity first checks for a free self-hosted agent, then for cloud profiles that can launch a compatible agent. If none are available, the build is offloaded to an executor.
Implicit agent requirements are now correctly recognized. Build steps can impose implicit tooling requirements on agents, like requiring Docker or Podman for containerized steps, or the .NET 8 SDK for .NET builds. As of 2025.07, TeamCity can correctly match these requirements with pod specifications, ensuring builds are never offloaded to executors that cannot run them.
Numerous bug fixes, such as resolving the ignored maximum build limit, PowerShell steps failing to run, excessive build log errors, and more.
Pipelines EAP
TeamCity 2025.07 introduces the first iteration of TeamCity Pipelines integrated directly into standard TeamCity On-Premises and Cloud servers.
Pipelines are designed for easy setup and include unique features like YAML support and an advanced visual editor.
Currently in Early Access, pipelines may lack some features needed for production CI/CD workflows. As such, they are hidden by default in the UI. Enable them by clicking Join Early Access program on the welcome screen or What’s New widget, or go directly to the Request Access page.
New Approval Rules
In Build Approval and Untrusted Builds settings, you can now combine individual users with user groups in a single entity with a shared vote count. For example, the following rule expects three votes to start a build:
These three votes can come from any combination of the specified users or groups.
Miscellaneous Enhancements
SSH keys uploaded to or generated in TeamCity are now stored encrypted in the TeamCity Data Directory in encrypted form. TeamCity uses a custom encryption key from the general server settings, or a built-in key if none is specified. Note that only newly uploaded or generated keys are encrypted, re-upload existing keys to apply encryption.
If the Kotlin DSL "pom.xml" file includes the
<kotlin.compiler.incremental>true</kotlin.compiler.incremental>line, TeamCity Maven plugin will now switch to the incremental compilation mode. Previously, this setting was ignored.
Upgrade Notes
Before upgrading, we highly recommend reading about important changes in version 2025.07 compared to 2025.03.
Fixed Issues
See the TeamCity 2025.07 release notes article for the summary of implemented features and fixed issues.
Roadmap
See the TeamCity roadmap to learn about future updates.
Update TeamCity On-Premises
We recommend using the Automatic Update for the easiest and most reliable upgrade. For more information on the upgrade process and available options, see Upgrading TeamCity Server and Agents.
To download a .tar.gz or .exe installer for any TeamCity major or bug-fix version, visit the Previous Releases Downloads article.
For TeamCity servers running in Docker containers, see this article.
Your Feedback Matters
We place a high value on your feedback and encourage you to share your thoughts and suggestions. See this link for more information: Support and Troubleshooting.