TeamCity 2026.2.2 and 2026.1.6 Bug-Fix Updates Released
Critical security and performance patches arrive for TeamCity On-Premises environments.
1Critical Maintenance Release
JetBrains has officially released TeamCity 2026.2.2 and 2026.1.6 to address identified security vulnerabilities and performance bottlenecks. These updates are specifically designed for On-Premises installations, ensuring that existing CI/CD environments remain protected against potential threats. Users are strongly encouraged to apply these patches immediately to maintain the integrity of their build pipelines.
2Resolved Versioned Settings Bug
A specific issue where projects created by parent projects with versioned settings failed to collect new changes has been fixed. This bug previously hindered automated synchronization, causing delays in build triggers. By resolving this, the update restores reliable configuration management for complex, hierarchical project structures within the TeamCity environment.
3Cloud Agent Matching Fix
The update resolves a critical failure where cloud agents could not be correctly matched to their related instances following a server restart. This synchronization error often led to orphaned agents and stalled build queues. The fix ensures that ephemeral cloud resources reconnect seamlessly, maintaining consistent build capacity after infrastructure maintenance cycles.
4Revision Calculation Optimization
Performance improvements target slow revision calculations for checkout rules, particularly for files that are rarely changed. Previously, these calculations created unnecessary latency during the build initialization phase. This optimization significantly reduces overhead for large repositories, ensuring that build agents spend less time on metadata processing and more on execution.
5Secondary Node Patch Retrieval
The update fixes a bug preventing secondary nodes from retrieving the list of available security patches. This issue previously created visibility gaps in multi-node configurations, leaving secondary infrastructure potentially unaware of pending updates. With this fix, administrators can ensure that all nodes in a cluster remain synchronized and fully patched.
6Seamless Upgrade Path
All bug-fix updates within the same major version share a unified data format, simplifying the deployment process. Administrators can upgrade or downgrade between these versions without requiring complex backup and restoration procedures. This architectural consistency allows teams to roll back quickly if unforeseen integration issues arise during the deployment phase.
7Deployment Options Available
Users can apply these updates through the built-in automatic update feature within their current TeamCity instance. Alternatively, administrators may download the latest binaries directly from the JetBrains website or pull the updated TeamCity Docker image. These flexible deployment methods accommodate various infrastructure setups, from traditional servers to containerized environments.
8Operational Stability Impact
Maintaining minor releases ensures better compatibility with third-party integrations and faster, more stable build processes. Beyond security, these updates provide the foundational stability required for high-frequency deployment pipelines. Teams should monitor the TeamCity Forum and Issue Tracker for ongoing support or to report any specific challenges encountered during the update.
Original article: The JetBrains Blog — TeamCity 2026.2.2 and 2026.1.6 Bug-Fix Updates Released