Released: Mar 4, 2024

Atualizações na 2023.11.4

Correções

• If TeamCity is unable to reach jetbrains.com, it can slow down the start of the builds as well as some pages.
• jacocoReport.xml is created empty due to ClassNotFoundError (if non bundled Jacoco is used).
• AWS instance role/profile permissions no longer used by EC2 Cloud Profile in 2023.11.3.
• Builds take incorrect revision if using settings from VCS and only negative checkout rules are defined.
• EC2 cloud profile configuration missing agent push preset.
• Cannot find a node:100479888 may occur when collecting VCS changes on the secondary node.
• Log statuses from Commit status publisher to the teamcity-commit-status.log.
• Regression: java.lang.InstantiationException: bean not found within scope while processing request.
• Agent JDKs: Clean Up JDK distribution if it was replaced.
• "Publishing build cache" build log is never closed after error, duration keeps increasing.
• Build Cache: Support parameter references in cache names.
• Updated TeamCity maven plugin to be compatible with 2023.11.
• S3 Storage new UI: unnecessary patch is generated after saving S3 settings using UI after TeamCity update.
• GitHub App installation token can not be acquired in Pull requests Build feature and Commit Status publisher if VCS Root URL has alternative scp-like syntax.
• Log info about agent, selected based on CPU, build duration and agent priority, to teamcity-server.log (debug).
• TeamCity server can't automatically restart.
• Cross-node event processing hangs due to a concurrency problem.
• Failed muted tests may produce failed build if server was restarted/changes running node.
• Flying loader on "show all N configurations".