Released: Nov 7, 2019

Updates in 2019.1.5

Fixes

Security Problem

• A major problem with potential exposure of some server-stored passwords to users without due permissions.
• Two problems concerning the possibility of a reverse tabnabbing in several TeamCity plugins.

Feature

• Use uploaded trusted SSL certificated for email notifications sending.

Usability Problem

• Experimental UI shows time since the build started instead of finished.

Bug

• [S3] Retry uploading to S3.
• ProjectManagerImpl.getProjectIds: Comparison method violates its general contract.
• Corrupted "Configure Build Agent Properties" Java window layout during agent installation under Windows 10 (bad bundled Java).
• More cloud agents can be started than there are available agent licenses.
• Performing a POST request using Bearer token returns 403 error of missing Origin header, same request with user+pass works fine.
• Infinite loop (and CPU load) calculating build committers for a notification.
• Filter by branches does not work in all Project tabs except for Overview tab.
• Chrome tab crashes with "Not enough memory to open this page" when leaved open on build step's page with many running builds.
• Can no longer use default credential chain in ECS plugin.
• Broken path to build.gradle file for autodetected build steps.
• Secondary nodes stops processing events after error 'Error while processing multi-node event: buildStarted'.
• Certain package doesn't get published to the nuget feed since version 2019.1.4.
• Server can get slow on build metrics retrieval (many different statistic values caused by custom build start precondition).
• Amazon ECR Connection: "Default Credential Provider Chain" option is no longer available after update to 2019.1.4.
• Build doesn't stop: "Data too long for column 'task_identity' at row 1" error.
• dotnet CLI agents part is not loading under Java 1.6.
• Browser auto-fill can suggest previously used passwords in "password" field for a certain setting.
• Build ends up in the top of the queue when stopped with "re-add to the queue" option.
• Empty password for run agent is displayed as not empty in Agent Push preset window.
• Cloud instances stuck in "will be stopped soon" status.
• Unnecessary build configuration ids group can be created in database if there is a hash collision of this group with another one.

Performance Problem

• Speedup agent pool expanding in case when there are many projects in the pool (17k active, 12k archived).
• Investigations auto assigner long running background threads.

Task

• Need to upgrade docker in teamcity-agent image to fix issue with unexpected docker stop.

Cosmetics

• Ambiguous message when waiting for to ‘Run build on the same agent’.