Overview

JetBrains released TeamCity 2019.2.2, a maintenance update to its CI/CD platform that carries enough security weight for the vendor to strongly recommend that all customers upgrade as soon as possible. Alongside the security patches, the release delivers over 60 bug fixes, more than 20 performance improvements, and three new features.

Security Fixes

JetBrains has not publicly disclosed the technical details of the security vulnerabilities addressed in this release, which is a common responsible-disclosure practice to reduce the window of opportunity for exploitation before users can upgrade. The fact that the company issued an explicit “strongly recommend” upgrade advisory signals that the issues are rated significant rather than low-severity. Teams running any earlier 2019.x release should prioritize this update.

New Features

Three new capabilities were introduced in this release:

• Multiple Docker accounts in Docker Support: TeamCity’s Docker Support feature can now be configured with more than one Docker registry account, giving teams greater flexibility when working across multiple registries.
• Agent pool type distinction via REST API: The /app/rest/ui/agentPools endpoint now differentiates between regular agent pools and project agent pools, making it easier to build automation and integrations that act on pool type.
• Dynamic build problem investigation UI: The UI now refreshes automatically when a build problem investigation is updated, removing the need to manually reload the page to see the latest investigation status.

Usability Improvements

Several usability pain points were addressed:

• Compact build configuration presentation: The Clean-up settings page now shows a compact view for build configurations derived from multiple templates, reducing visual clutter.
• Name truncation fix: Names in the UI are no longer shortened unnecessarily when sufficient horizontal space is available.
• Build results auto-update: A bug that prevented build result information from refreshing automatically after a build completed has been resolved.

Bug Fixes: UI and Functional Issues

The release closes a broad set of UI and functional defects, including:

• No error message being displayed when branch retrieval for a drop-down control failed.
• The “Show all build problems” button on the build page rendering no results despite problems existing.

In total, more than 60 issues are addressed across the UI, VCS integrations, REST API, and build runner components.

Performance Fixes

More than 20 performance-related fixes are included. A notable regression introduced in 2019.2.1 caused TeamCity to run very slowly after upgrading; this is resolved in 2019.2.2. Teams that deferred upgrading to 2019.2.1 due to performance reports should find 2019.2.2 significantly more stable.

Database Layer Improvements

Several fixes target the database layer, which is critical in large TeamCity installations:

• LIMIT-style query support for Oracle and MS SQL: The DB layer has been extended to support row-limiting queries on Oracle and Microsoft SQL Server, improving compatibility and query efficiency on these backends.
• Connection pool exhaustion on high-core-count servers: A particularly impactful bug was fixed where servers with many CPU cores could stall with the error “Database connections pool exhausted” when disk I/O became slow due to a high number of threads writing load simultaneously. This is a significant stability fix for large, busy TeamCity installations.

Upgrade Recommendation

Given the combination of undisclosed security vulnerabilities and confirmed performance regressions fixed in this release, upgrading to TeamCity 2019.2.2 from any earlier 2019.x version is strongly advisable. Consult the official JetBrains TeamCity page and the TeamCity release notes for the full changelog before upgrading in production environments.