TeamCity 2017.1.4

Usability Problem

• Permission name "View available images and running instances" is confusing.
• Do not detect gradlew.bat as an executable.
• Make critical server health items related to a build configuration more noticeable.
• Gradle step settings view should show working directory.
• Display icon for Info health items in Health popup.
• User without VIEW_AGENT_CLOUDS permission (default project developer) see No Compatible Agents when first cloud agent is starting.
• Show agent name prefix in images table on edit cloud profile page.
• Misleading message when versioned settings are disabled after upgrade with converters.

Bug

• Error during import of DupFinder xml report.
• Gradle parallel execution may fail to report service messages properly.
• Wrong test results when tests run via gradle in several threads.
• Improve Gradle build problems reporting: unclear "Using experimental kotlin incremental compilation" compilation error.
• Validation for an uploaded JetBrains dotCover/ReSharper CLT is case sensitive.
• Jabber notifier stopped working after upgrade to 10.0.4.
• No error is displayed in UI on error retrieving branches for drop-down.
• On Mac agent launchd.out.log log file may occupy too much space.
• "Value cannot be null. Parameter name: enumerable" during Personal Build scheduling via VS2015.
• Build queue consumed 3 Gb of memory in Chrome.
• Build Queue page open for hours crashes the browser tab.
• Visual Studio remote run: build customization doesn't work.
• Weird behaviour in the "Investigations" tab.
• Check work with TFS proxy server in java and .net modes.
• Newly introduced inspection warnings not shown for personal builds.
• Build page might not be reloaded after build finishes.
• Problems with viewing all registered users after the upgrade to 2017.1.x.
• NuGet packages from the fresh builds might not appear in the feed for a long time after cache reset (until all the builds are re-indexed).
• Build revision changes after build with custom VCS root or checkout rules.
• Normalize URL in breadcrumbs.
• Commit Status Publisher generates invalid JSON.
• TeamCity may create a corrupted database backup because of compatibility problems in MS SQL Server JDBC driver.
• Unable to ignore a test with a non-ASCII name longer than 255 characters.
• Attempt to open issue details popup from changes popup closes the changes popup.
• Password parameters not obfuscated in build log when set using Build Script Interaction.
• First project created after user was registered during invitation flow is not visible on Overview page.
• Snapshot dependencies of a build can be lost (build start without dependencies) on specific queuing sequence with builds promotion.
• REST: Wrong "href" attribute value for some versioned requests (build artifacts and others).
• Build configuration doesn't checkout the latest commit in one of repositories.
• Add git to server docker image.
• Failed to publish artifacts because of colon (:) in artifacts path created by TeamCity (Meta-runner with NUnit step).
• Build with the 'teamcity.buildRevisions.detectUnknownCommitMerge' option doesn't select the latest merge commit.
• Do not terminate outdated cloud instances without agent.
• cache folder in the server, When Datadirectory is on share.
• "'2.482336912E9' in column '2' is outside valid range for the datatype INTEGER" when estimating row counts during backup.
• Critical error in configuration file %PATH TO FILE% Project with name "%NAME%" already exists.
• Some strange logging on TeamCity server start (Unable to locate project for cloud profile 'amazon-3').
• Set up new TeamCity server: no error message is displayed for administrator account password mismatch.
• SBT 1.0 Support Sbt runner fails with NoClassDefFoundError: sbt/Plugin.
• Failed to filter NuGet packages in feed via NuGet client 2.8.2.
• java.lang.NullPointerException during getting compatible agents.
• NPE from BranchNameGenerator.generateBranchName makes build failed with single "Failed to start build" message in the log.
• Not all build log can be shown without any related notes.
• Generated Kotlin configs don't handle several artifact dependencies on the same buildType.
• Create build config form does not update the list of available templates when a parent project is changed, and displays an unpleasant error message if submitted.
• Outdated build configuration settings on overview after settings update from VCS.
• Current repository changes might be occasionally not included into a build (outdated revision is used) when there are several VCS roots and one if DAG-based.
• "Versioned settings disabled" health report is not shown if versioned settings are disabled in all projects.
• Provide images names/ids in Terminate Instance dialog.
• Drop down lists are still displayed after Edit Image dialog is closed in cloud profile.
• Cloud instance is considered as running by other TeamCity server if you decide to use it in another cloud profile.
• No enabled compatible agents is shown to project developer without VIEW_AGENT_CLOUDS permission.
• Do not show Agents -> Clouds tab to user if all projects where he/she can see cloud agents do not have cloud profiles.
• Permission VIEW_AGENT_CLOUDS is checked incorrectly.
• Cannot download build artifact from UI (build Dependencies tab) if there is '+' symbol in the path.
• ProcessTreeTerminator does not support Windows Nano Server.
• Schedule trigger DSL doesn't have API for branchFilter parameter.
• Schedule trigger cron compound parameter in DSL doesn't have timezone option.
• Deadlock during applying configs changes from VCS and new VCS root/project creation.
• Failure with HSQL DB initialization in Windows docker container.
• Improve incorrect CTest results parsing.
• Project settings changes from VCS can be applied out-of-order.

Exception

• Cannot find or load main class during manual backup.

Performance Problem

• Slow finishing of builds in case of many rows in mute_test_in_proj table.
• Too long build results page load as BuildStatisticsBuilder.fillFixedIn can iterate through large number of builds executing thousands of queries.
• Inefficient code in jetbrains.buildServer.clouds.server.instances.BuildStartFilter can occupy plenty of CPU.
• Eliminate global lock in ExitCodeBuildProblemRenderer.
• Support bulk operations in TFS personal support.
• QueueStateManagerImpl.readQueueState can slow down processing of the builds in the queue.

Security Problem

• Possible HTML injection in email notifications.

Cosmetics

• Filter reset 'cross' item can detach from the filter button on Audit page.
• Incorrect tool-tip for <_Root> in server Health Items popup.
• Extra newlines in build problem description (gradle parallel execution).