Released: Jul 23, 2025

Mises à jour de 2025.07

Fonctionnalités

• UI Improvements
  • 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
  • 2025.03, announced a shift from meta-runners to recipes: lightweight, YAML-based custom steps available on JetBrains Marketplace. At the moment, the Marketplace offers more over 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.
• 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.
  • This release implements multiple new options that allow you to set up periodic workspace clean-ups.
• 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.
• 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.
• 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.
• 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.
  • The Parallel Tests build feature now includes the Artifacts setting that allows TeamCity to categorize artifacts into "Batch N" folders on the main build results page. Previously, you had to implement this behavior manually by adding the teamcity.build.parallelTests.currentBatch parameter reference to artifact paths.
  • 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.