Looking for TeamCity hosted by JetBrains? Please see TeamCity Cloud.
TeamCity 2019.1.3
Released: Aug 29, 2019
2019.1.3 での更新項目
不具合の修正
Usability Problem
Do not scroll sidebar after selecting item, which belongs to favorites.
Trends and builds list show different last build.
Bug
Extremely long service message does not catch failed test.
Lock wait timeout in MySQL while updating last login timestamp.
Docker Compose: run chown to restore file permissions on Linux after the build.
After upgrading, TeamCity is not finding changes for branches and pull requests built before upgrading to 2018.2.
"The build was triggered in the branch which does not correspond to any branch monitored by the build VCS roots" can be displayed for some pull requests.
Build can be started on the default branch instead of a PR head when re-running build for some pull requests.
MySQL LockWaitTimeoutException from VcsModificationsStorageImpl.persistModification.
Many redundant builds on old branches can be triggered (schedule trigger with only build on pending changes, yet there are no changes in the builds).
Pull-request plugin doesn't work for PR when the build feature was added after the PR was created.
Configured custom server context is ignored when NuGet Feed is created.
Provide a way to disable Experimental UI for all users.
Incorrect link in build log.
Show GitLab v3 related stacktrace only in DEBUG mode.
Build in GitLab merge-requests fails to start.
YouTrack integration can produce 401/Unauthorized errors for long permanent tokens.
Cloud profile falls into an error state when looking for a task that doesn't exist anymore. ECS Plugin.
Requirement for teamcity.tool.* parameter makes agents incompatible until the tool is downloaded.
Change's related builds finding can be broken: shows unrelated builds, does not show the proper ones.
Pull request build feature sometimes fails to provide branch specs for old pull requests with new commits.
Docker Wrapper scripts have to escape '|' character (at least in Project Name).
Subsequent builds are cancelled with comment "Agent runs unknown build we're not aware of" (pending commands related to execution timeout are in the messages queue).
List of builds for all build configuration will be empty after switching from favorites builds.
dotnet test failed to run test after update to 2019.1.2: .NET SDK was not found.
Builds showing as hanging server-side but agent has finished.
Collapsed parent of a selected favorite item doesn't get selected.
Incorrect failed NUnit tests count (tests print to standard output and the output doesn't end with a new line).
TeamCity reversed the order of Perforce client name generation.
"Old Java version" health item refers to 1 agent when there are more than 1.
Server may not start if catalina.out file becomes large.
Assertion error in ConfigChangesCommitterImpl.onProjectRemove.
"Build is running" indicator is frozen on tiles in Experimental UI.
"Couldn't initialize a SAX driver to create an XMLReader" exception when TeamCity tries to clean up artifacts in S3 with temp credentials.
View DSL doesn't work for build step when UI editing is disabled.
Verify email fails with log message "Attempt to use email sender before server is initialized".
Build list always is filtered by a specific branch name if branch in classic UI was chosen.
View DSL action changes settings on disk (stores inherited build steps as overridden) when step editing is disabled.
File Content Replacer doesn't allow multiple lines in the UI, and "\n" doesn't introduce a new line, but it works if using parameters or versioned settings.
PullRequestBranchFullInfoExtension adds blank 'page fragment' to every build overview page.
Unexpected error while access token creation.
Performance Problem
Excessive memory usage inside XML RPC request processor.
Method ModificationDAGInt.getNodesWithoutChildren can consume a lot of memory.
Lots of threads blocked on handling '/app/agents/protocols' after restart.
REST: Slow change finding by version.
Slow health report SwabraCleanCheckoutWatcherImpl.getRecentCleanCheckoutCauses because of inefficient storage of health report related data.
Slow calculation of health status item visibility because of many SQL queries on a server where many health items are detected.
Task
Get rid of ZeroClipboard.swf.
Update bundled ReSharper CLT to 2019.2.1.
Cosmetics
GitLab Connection button on create project/VCS root form has a duplicated label.