Features

• Added the ability to show statuses and counters of non favorite build types and projects in sidebar.

Fixes

• "Managing Projects and Build Configurations" page is not about managing projects.
• Create from URL fails for GitHub with Not Found (404) in case of password authentication.
• Don't show the artifacts isolation health report if artifacts URL isn't configured.
• Unable to re-run a build if there is no CUSTOMIZE_BUILD_REVISIONS permission for its dependency.
• Make the Parameters tab default again in comparison.
• Applying patch changes adds characters at the front of file.
• "Too many open files" error during agent startup on some systems.
• A lot of memory occupied by Lucene build indexer (600M ScoreDoc instances).
• NuGet Trigger doesn't work with multi-node setup and enabled process trigger responsibility.
• AWS cloud agent machine is never removed.
• GitHub Commit Hooks plugin does not always persist last commit hook information and may unreasonably clean up working commit hook settings.
• Python runer left script file in buildTemp directory.
• DSL patch is generated when adding a project parameter (if config version from settings.kts file does not equal to the current server config version).
• Amazon ECR Connection ignores IAM Role specified.
• Tests can point to the wrong position in the build log.
• VCS trigger may not trigger a build in case of a change in settings VCS root and branch move in a regular VCS root.
• Limit build artifacts highlight width in the experimental UI.
• Failed to fetch the issue, reason: Unexpected JSON type: class com.google.gson.JsonPrimitive.
• VCS trigger with quiet period does not trigger build on branch move.
• Schedule trigger triggers builds in obsolete branches if branches temporary disappear and then reappear again.
• Schedule build trigger runs build without changes.
• Ignored maven.repo.local when not reading the pom.
• Disable jgit internal auto git gc.
• Copying of secure values on the Tokens tab can cause a commit of the project settings to VCS.
• SSH Exec: Username field is ignored for 'Default private key' if there is an ssh config on the agent host.
• GitHub commits hook plugin is incompatible with TeamCity 2020.2.
• Audit: 'User was created' records have incorrect value in User field.
• MultiNodesEvents usage prevents plugin from upload without server restart.
• TFS Workspace deletion.
• Don't show configure sidebar dialog for an empty server.
• Impossible to use repository with "--config".
• Dependencies comparison doesn't work when there are no common dependent builds for chosen builds.
• Unexpected error "bean newVersionBean not found within scope" for non-administrators on the health item.
• Problem investigation with manual resolution removed automatically after successful build and clean-up.
• Restore "teamcity.git.use.shallow.clone" support for shallow clone from mirror to checkout directory when alternates are disabled.
• Too much memory occupied by Lucene Document instance.
• High memory usage due to absence of limits in tracing code.
• Github is deprecating support for password authentication for git operations.
• 5 security problems have been fixed.

Features

• When you create a project or build configuration from a Git repository URL, TeamCity now allows you to change the default branch and branch specification right in the creation wizard.
• If you prefer the users of your TeamCity server to authenticate through third-party services (for example, GitHub), you can now globally hide the default username/password login fields. This way, users will not be distracted by the built-in authentication form and will smoothly proceed with the available authentication options.
• Performance fixes for faster operations and better hardware utilization.
• Small enhancements for the experimental UI.

Fixes

• New tab extending AgentDetailsTab does not show in experimental UI.
• Wait reason for queued builds is updated with a delay.
• Viewing full test stacktrace on build results requires additional clicks/scrolling.
• Hide/collapse basic auth login fields for customers using alternative auth mechanisms.
• Python runner. Provide some hints about how to specify test/inspect objects for pylint/pytest/flake8.
• Show build branch name in personal Slack notifications.
• Sakura: don't hide tabs on overview pages.
• Branches are not built by default when creating project from Git repository.
• Sort context parameters on versioned settings page (alphabetically).
• Agent page: keep selected tab when switching between agents.
• New Queue page: estimated finish time and build duration are not displayed.
• Cannot globally re-enable Versioned Settings after upgrade.
• VCS trigger skips triggering on new pending changes after modification of the VCS root.
• Detached interrupted build can remain running on server.
• Could not find a test logger with AssemblyQualifiedName, URI or FriendlyName 'logger://teamcity/'. on .NET 5.0.103.
• Cancelling build with service message doesn't work for builds with detached steps.
• .NET runner ignores Test case filter parameter.
• ERROR: out of shared memory.
• Problem with NuGet Dependency Trigger - Failed to check for package versions.
• Build log on overview displays verbose messages as normal ones.
• Incorrect pending changes in a build configuration with checkout rules after VCS root editing.
• Build can be marked as failed if it has non branched VCS root (Perforce, SVN) and implicit versioned settings VCS root and is triggered in a logical branch.
• External artifacts for composite builds aren't displayed on the secondary node.
• expired EC2 cloud instance can be terminated before the build is finished.
• Can't see Dependencies of a build in new UI while old shows them just fine.
• "Build log messages" block on Build Overview is not being refreshed.
• Wrong number of projects displayed in agent pool.
• Build configuration or template with ID "<some id>" has the same uuid error after template ID change with versioned settings enabled.
• Provide better DSL for TestNG reports in XML report processing build feature.
• Lots of projects were not loaded on server start which led to removal of several queued builds.
• Provide better DSL for XML report processing build feature.
• Empty tests list for personal builds in Experimental UI.
• Agent on Mac exposes several JAVA_MAIN_CLASS_XXX environment variables.
• Endless loop requests queued and non-queued builds.
• Just finished build has been removed by cleanup.
• "Unauthorized" section disappears from Agents sidebar when there authorized agents are disconnected.
• NaN build is running, undefined agent is idle is shown in the header during agents update.
• New changes may not be attached to a build configuration if the configuration belongs to a project where versioned settings are enabled.
• Possible general changes collection slow-down because of retry for git roots.
• Builds do not start waiting to lock a single VCS Root instance for a long time, CPU 100%.
• Open Agent pool page by default when a new pool is created in Experimental UI.
• Missed Start Page property in Kotlin DSL.
• Automatic Update hangs with "Server was stopped to update, but didn't start in 120 seconds, see logs/teamcity-update.log for details.".
• Agent pools page in Classic UI should not redirect to the Experimental UI.
• Support EdgeHTML 18.
• "Show root cause only \ own problems" selector always shown on the build overview page.
• Copy build configuration with emoji - "Failed to log action to audit. Incorrect string value".
• Incorrect build and files are displayed in Artifact Dependency Change section in new UI.
• TeamCity Updater: use the SSL certificates uploaded to root project.
• Python pylint inspection does not report "Fatal errors" as errors.
• New Agent Details page: Update Java dialog doesn't open automatically.
• Busy agent is shown as idle for user who doesn't have permissions to see the running build details.
• Build queue pager shows wrong number of builds and wrong link, if requested page does not exist (too few builds).
• Cleanup: CleanupExtensionsExecutor#fixOldBuildsArtifactsDirectory calls can take a lot of time when there are a lot of builds that were created by old TeamCity.
• Calculating short statistics does not cache results in runtime for new test failures for running builds.
• Slow processing of cleanupFinished event if a lot of changes are unloaded from cache at once and there are many thousands of build configurations.
• Calculating short statistics for a complex build with failed tests may hang UI for many users in a case of large build history.
• Additional copy files operation can slowdown freeze of queued builds settings.
• Slow working CommittedBuildsUpdater thread can accumulate a lot of running builds in its queue.
• Inefficient processing of builds deletion from builds metadata index.
• Endless loop in EMailNotificator.sendToAddress in case of enabled debug logging.
• Lots of build problems reported for some build on a secondary node can greatly reduce build queue processing time on the main server.
• Suboptimal import of tables during projects import.
• BuildQueueCountersByPoolNotificator constantly consumes CPU.
• NotificationProcessor threads can occupy significant amount of CPU while they compute build committers.
• BuildPromotionImpl.isIncomplete() invoked on a personal build which was interrupted because agent its disconnected can cause major slowdown.
• Python script with non-ASCII symbols in name. Bad encoding in build log in case there are syntax errors.
• Inconsistent capitalization in Python build step.

Features

• Added new Build Queue page.
• Added the ability to create an agent pool in the new UI.
• Added support for multiline values in Secret Tokens.
• Added the ability to cancel long-executing tasks on the 'Settings Persist Status' tab of the Diagnostics page.
• Added support for connections in usage statistics reports.
• You can now show tests in failed order on build page.
• Added the ability to delete secure token values.
• Added the commit date as an attribute to VcsModification.
• Edit sidebar: Added 'Reset order' button.
• Added split flake8 inspection messages to several categories.
• Added split pylint inspection messages to several categories (i.e. by checker).
• Artifact tabs containing HTML should now be able to handle links to a directory.
• Microsoft .NET CLI should skip dotnet-core-runtime installations and find dotnet-core-sdk only while searching for .NET executables.

Fixes

• Python is not detected on Linux agent. IllegalStateException: System.getenv("path") must not be null.
• Add processing of test absence on the test history page (page 404).
• re-run build not restoring Dependencies used.
• Build log is empty for passed tests in experimental UI.
• S3 Artifact storage upload intermittent 403 failure.
• Re-run build dialogue: failed dependencies isn't re-used by default.
• Warning "This node cannot modify configuration files on disk" is displayed on the secondary node after copying a value for a token from another project.
• Agent page: support "Show date/time in my timezone" setting.
• TeamCity docker events processes may be not terminated.
• Don't mark tests as passed when build is cancelled.
• Add checksum verification to Windows-based docker images.
• NaN build is running, undefined agent is idle is shown in the header during agents update.
• $commented magic word search doesn't work for non-pinned builds.
• Queued build page. Reasons are endlessly loading in Build Details..
• Unauthorized agents page: redirect to the overview when the last agent was authorized.
• New UI: Agent summary screen gets 404 errors when agents deregister.
• The header is not shown in Classic UI.
• Build configuration overview page is not properly refreshed when the build is removed..
• Commit Status Publisher may cause overflow of the thread pool it uses and of the multi-node task queue as a result.
• Cleanup: PriorityClassManagerImpl#savePriorityClasses calls can take too much time when there are a lot of removed build configurations.
• catalina.out: many warnings like 'org.apache.catalina.webresources.Cache.getResource Unable to add the resource'.
• GitHub authentication: 'You don't belong to the allowed GitHub organization' when the TeamCity OAuth is not approved in organization settings.
• 2020.2.1 agent Docker image doesn't upgrade properly against 2020.2.1 server with changes.
• Perform schedule trigger invocation after server restart.
• Issues tab is absent on build.
• Build can consistently take obsolete revision if branch pointer was moved and VCS settings changed.
• Reset all button in the Dependencies tab of the custom build dialog doesn't work.
• Possible general changes collection slow-down because of retry for git roots.
• Error calling method BuildServerListener.buildFinished for listener org.jetbrains.teamcity.docker.serverHealth.ImagePullingWithoutAuthHealthReport$1.
• Some versioned settings not applied unless new commit.
• Overview / Project: buttons "Add new.." appear, even if UI editing disabled prior to DSL.
• Build History page for agents is jumping during scrolling.
• Can't check for EC2 options if there's an unknown region.
• Agent page. Experimental UI shows enable/disable agent comment with guillemet quotation marks and redundant line break.
• Message about lack of permissions divided into several lines on Agents -&gt; Overview (on pools) page.
• Information about test results isn't published in Bitbucket 7.5.0.
• "Copy to clipboard" action on the Docker tag opens a new tab with docker table.
• Excess and wrong statuses can be published on Builds tab in Bitbucket 7.4.1+.
• TeamCity doesn't handle non-URL encoded +'s in links inside reports.
• dotnet vstest command does not work in docker with error: The Test Logger URI 'console:verbosity=normal' is not valid.
• 'Could not deserialize versioned settings status from JSON' error.
• A new build configuration created in a non-default branch of versioned settings can break its build chain without reporting any problems.
• Queued builds list can be cached and displayed in wrong pool.
• Agent fails to checkout when using git 2.30.
• The same changes appear in two consecutive builds if a force push occurred.
• Queue page: actions button moved down if tags were added for a build.
• Notifications build feature: Suggestion of available parameters doesn't work for Send to EMail field.
• Build can be mistakenly marked as incomplete in the database if it finished on the secondary node but main node still thinks it is running.
• Unable to restart server run from jetbrains/teamcity-server (Windows based).
• A change from dependency is not shown as pending in a branch but is shown in a build in this branch once it starts.
• Changes in dependent builds are affected by a build in default branch of some dependency.
• Parametrization is limited for new Build Feature - Notifications.
• Docker build additional arguments revert to --pull if set blank.
• "Project scope" drop down in Investigate/Mute dialog can turn into text without ability to turn it select another project.
• Build canceled message is written inside the step section on the third level.
• Improve warning message in the server log when Perforce server is down.
• VCS root from GitHub OAuth connection sometimes auto-populates credentials password, sometimes doesn't.
• Whitespace triggers Kotlin DSL patch generation.
• Calling the backup rest api results with an error: Responding with error, status code: 415 (Unsupported Media Type)..
• VCS trigger triggers builds in non default branches on old commits.
• User without global permission to edit group cannot edit group if it has no roles assigned.
• OOME: git integration may consume a lot of memory when collecting changes for submodules.
• gp3 EBS volumes cannot be used in AWS Cloud provider plugin spot fleet requests.
• Handle situation with non-working links in the custom report tab.
• Secondary node: Build Queue priorities are not replicated to the main node..
• Lots of threads hanging computing tests statistics for a composite running build.
• ObsoleteFilesCleaner thread produces a lot of garbage while it processes directories.
• Starting with 2019.2 VCS trigger works much slower if build configuration monitors tenths of thousands of branches.
• RecentlyFailedTestsCalculator may prevent build from starting.
• Inefficient generation of pre-signed URLs in S3 storage plugin.
• [S3 Storage] Excessive sockets usage for presigned upload.
• New Queue page sends a lot of HTTP requests.
• Possible high CPU usage in server side patch transferring code.
• The queued builds page is loading slowly when a lot of builds are added to the queue..
• Build configuration history page is slow on first opening or reload (new UI).
• Fixed issue with TeamCity IntelliJ Plugin SSRF - A vulnerability that could have potentially exposed credentials of users who sign in to TeamCity from the IntelliJ plugin.
• Fixed issue with TeamCity IntelliJ Plugin DOS - A vulnerability that could have made DoS possible.
• Risk of potential TeamCity server DoS via server integration.
• Risk of potential XSS on several pages.

Features

• Added the ability to allow Amazon S3 upload chunk size and minimum multi-part threshold to be configurable.
• Added the ability to allow external connections from Java agents on the secondary node.
• Added Health reports for build configurations which do a Docker pull from Docker Hub without prior authentication.
• You can now build duration charts for the Test History page.
• Added the ability to see report progress when publishing to S3.
• Chain view: composite builds are now grouped by default.
• Added the ability to promote a build from the dependencies list.
• Agent compatible configurations tab: Added the ability to design how the agent incompatibilities should look.

Features

• Added support for authentication using external services: GitHub, GitLab, and Bitbucket.
  • You can instantly match external OAuth accounts with existing TeamCity users, and let them work with their projects without having to enter a password.
  • Added the ability to integrate with user directory features of the supported services, such as GitHub organizations and GitLab groups, and can automatically create new profiles when new members join your team.
  • Added support for on-premise installations of GitHub (GitHub Enterprise) and GitLab (GitLab self-hosted).
• Improved integration with Bitbucket Cloud by adding support for pull requests.
  • You can now set up TeamCity to automatically pick up pull requests made in your Bitbucket Cloud repository and run the respective builds.
• Added new Python build runner which enables you to use TeamCity in your Python projects.
  • The new build runner works with all operating systems, supports virtual environments, and integrates with all common testing frameworks and code inspection tools for Python.
  • The results of your Python builds and tests are reported in the TeamCity UI, in the same way as with all other TeamCity build runners. You can track changes, analyze failures, assign investigations, and use all the other TeamCity features currently available.
• Jetbrains Space is now supported by the Commit Status Publisher feature.
  • Commit Status Publisher will now automatically send the status of your builds to Space, letting you see it on the Commits page of your project.
• Your builds can now execute their final steps in agentless mode, releasing the build agents and allowing them to run other queued tasks.
  • TeamCity displays agentless build steps as standard builds and will enable you to track their status, browse their logs, and view their history.
• Added the ability to edit project-level settings in secondary servers. This enables your team to set up new builds while the primary server is under maintenance.
• Added the ability to see the disk space occupied by builds not only on your local drives but also in remote locations.
• You can now customize the clean-up schedule with the use of cron-like expressions to have the server cleanup start at regular intervals.
• Improved the Build Dependencies page:
  • The Timeline view now shows not only started and finished builds but also queued builds.
  • The Build Chain view now shows the “right” part of the chain: all builds that depend on the current one.
• Added new Test History page to the Sakura UI. The new page gives you detailed information on your tests and allows you to analyze trends, see investigation history, and more.
• Added the ability to search the build log.
• Sakura UI plugin development framework: Added a new way to write and integrate plugins for the user interface.
• Added a new Build Queue page which lets you quickly see the changes for every queued build, understand what triggered the build and where it will run, get the estimated time when it will start, and view all the other build information in a neat and convenient UI.
  • You can select any builds that you don’t need and remove them from the queue, or alternatively, if there are builds that need to complete sooner, you can move them to the top of the list.