Released: May 3, 2024

Mises à jour de 2024.03.1

Correctifs

• NuGet feed auth fails with error 401, if NTLM auth module is enabled on the server.
• Confusing message "Gradle's configuration-cache is enabled" in the build log if the old Gradle version and incorrect configuration-cache parameter are used in the project.
• Upload custom tool fails with error "Failed to move the unpacked tool from the temporary directory".
• Builds in default branch do not start, if fallback to default branch is disabled.
• Agent - Disconnected, Unregistered because of inactivity.
• Build Status icons are shifted 1px left.
• Agent checkout of TFS repo failed with "Problem while checkout on agent: java.lang.NoClassDefFoundError: javax/activation/DataSource".
• "bean currentUser not found within scope" error in the logs when an unauthorized user opens a non existing page.
• A lot of NPEs may be logged if caching estimator was unable to initialize.
• Classic UI build status icons are always grey.
• Classic UI: Stop the run button disappeared on project/overview pages.
• Request authenticated via Build credentials fails with "You do not have enough permissions".
• New EC2 UI User Data field: pressing "p" key opens project popup.
• Empty response body for 401 unauthorized error in 2024.03+.
• Misleading documentation for scheduled trigger with build change.
• 400 (Bad Request) page at attempt to open overview of Canceled build that required approval from Untrusted build feature.
• TeamCity process environment fetcher plugin corrupted jar reported by TeamCity.Node plugin.
• Bitbucket server: OAuth sign-in can fail to fetch current user.
• "Internal error occurred" in Docker Compose builds running on podman agents.
• Can't connect GitHub Enterprise and Space account with TeamCity user account in user's profile.
• Add new parameter dialog: set cursor after parameter kind when system or env parameter is selected.
• Allow to modify read-only parameter value when parameter spec is editable.
• Images pushed by podman are not cleaned up by Docker support build feature.
• GitHub publisher should parse errors in HTTP response and report it to the user.
• Failed to perform checkout on agent: Problem while checkout on agent: java.lang.IllegalStateException: @NotNull method jetbrains/buildServer/vcs/perforce/ClientNameBuilder.getWorkspaceName must not return null.
• Refreshable token cannot be used in commit status publisher if vcs root is defined higher in the hierarchy than GitHubApp connection.
• A build does not start for hours, until server restart.
• Possibility to obtain non-GitHubApp token with "GitHubApp token" authentication type.
• Docker-compose runner doesn't work with a podman-compose.
• Plugins which depend on rest-api plugin are not reloadable.
• Implementations of JerseyInjectableBeanProvider in plugins are not registered in the container.
• Untrusted builds: excessive logging for canceled builds.
• Retry trigger does not retry a build on the same revisions while there is a running build already.
• Agent link for dead cloud instance should lead to a cloud image instead.
• Untrusted builds: Auto-approval doesn't approve generated subbuilds.
• Wrong time unit (milliseconds instead of seconds) in "Time saved by reusing dependency builds" statistic value.
• "Time saved by reusing dependency builds = 0" is reported to statistics, if reused dependency was already running when composite build was started (optimized chain).
• Confusing logging of user creation.
• Build agent's lib dir isn't accessible while building in a Docker container using a TC agent from a Docker image.
• The JSON body should contain a list of builds in the "Reusing Builds with Indirect Dependencies" section.
• Add a note that no security patches are currently available for semi-automatical installation.
• Visible HTML tags in displayed health items.
• Build Artifacts: Files considered folders in some cases.
• Commit Status Publisher submits multinode tasks for all build configurations.
• Slow triggers processing possibly because some of the VCS commits are unloaded from the cache because they are too old.
• Improved performance of multi node tasks processing.
• Improved performance of builds filtering with help of sinceBuild/untilBuild in REST API locator.
• Project loading may consume all memory in case of a cycle.
• Inefficient code in Change.isVersionedSettings possibly leading to higher CPU usage.
• 2 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.