TeamCity 2025.03.2 Release Notes
Build 186181, 8 May 2025
Bug
TW-92994 — project-config.xml file not created for large project copy
TW-93187 — Builds get stuck in the queue with "no idle compatible agents" due to an undiscoverable cloud profile error
TW-93101 — Repeating attempts to stop the build are too fast (20 secs)
TW-92997 — Regression: cannot upgrade to 2025.03.1, enqueues thousands of builds
TW-92878 — Artifacts Migration tool: a lot of messages like "failed to copy '34' artifacts" in migration tool output can be shown even if artifacts were copied
TW-92653 — Cloud agents don't start if plugin with agent part is enabled or upgrade of TeamCity took place
TW-92917 — Agent git mirror is cleaned if remote server hangs up
TW-90677 — Kubernetes Executor: cross-platform msbuild is stuck
TW-89671 — No coverage results, "Failed to find dotCover"
TW-92586 — Unaligned buttons in Project Settings -> Untrusted builds
TW-91646 — Region from the last created AWS EC2 profile is used instead of the opened one
TW-92404 — Add Image dialog shows old list of AMIs after changing Region in AWS Cloud Profile
TW-92498 — BuildAgent may hang on a faulty artifact publishing command
TW-93055 — Hard to follow documentation on nested test reporting with service messages
TW-91323 — Update the description of the "Project Administrator" role by adding information about the visibility of the Root project
TW-92895 — Error "Container wrapper is not supported" during usage of "Run in Docker" build feature if "Image platform" was chosen in the build steps
TW-92939 — RequiredToolInstalledPrecondition pollutes logs when build type is removed
TW-88707 — EC2 Cloud Profile: When there aren't enough addresses in one subnet, another should be tried
Security
Four security problems have been fixed. This number includes both native TeamCity issues and vulnerabilities found in 3rd-party libraries TeamCity depends on. Upstream library issues usually make up the majority of this total number, and are promptly resolved by updating these libraries to their newest versions.
To learn more about fixed vulnerabilities directly related to TeamCity, check out our Security Bulletin. Security bulletins for new versions are typically published within the next few days after the release date.