Loading…
Topic
6 posts about TeamCity. Every summary links to the original.
See the idea
Buildkite splits CI into a hosted control plane and agents you run on your own machines. This comparison weighs that self-hosted agent model against fully hosted runners so you can pick the right fleet.
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Newest first
The Warm Agents plugin for TeamCity reduces build queue time by maintaining a target number of idle, pre-started cloud agents, addressing the delay when builds wait for a starting agent. When idle agents drop below the target, TeamCity automatically provisions a new instance from the cloud image, ensuring builds start immediately; instances start in batches with short delays. The plugin works with any cloud provider TeamCity supports, requires TeamCity 2024.12.3 or later, and respects the cloud image’s hard limit on total running agents. Administrators configure warm agents via REST API calls, setting a target count per cloud image, and can schedule target changes using build triggers to scale down overnight and restore in the morning. The plugin trades cost for latency, as each idle agent consumes a build license and cloud instance cost, and exposes utilization and saturation metrics in Prometheus format.
JetBrains has released TeamCity 2026.2.1 and 2026.1.5, two bug-fix updates for the On-Premises versions of TeamCity that address more than 40 security vulnerabilities combined. These updates also resolve specific regressions including TFS projects failing to display diffs, YAML configuration import issues from a main repository branch, and MSBuild tools not being detected after the Visual Studio Build Tools 2026 September update. In addition to the numerous security fixes, these releases deliver performance improvements, better compatibility with integrations, and faster, more stable builds for users. A key compatibility feature allows upgrades or downgrades within the same major version without requiring backup restoration because bug-fix releases share a common data format. Users can upgrade via automatic update within TeamCity, direct download from the JetBrains website, or by pulling the updated Docker image from Docker Hub.
The post describes the design of a new TeamCity integration for Kotlin Multiplatform (KMP) developers building iOS apps. The integration addresses common pain points: iOS builds require macOS infrastructure, Apple signing is complex, and there is no guided path from IDE to CI/CD. The solution provides a progressive onboarding flow within the IDE, starting with a tooltip after the first Git push. The flow generates four configuration files (teamcity.yaml, Fastfile, Appfile, Gemfile) and runs a build and tests on a hosted macOS agent, then guides the developer through a single form for Apple signing and TestFlight publishing, and finally automates the pipeline on GitHub pushes. TeamCity Cloud provides hosted macOS agents and a free starting tier, so no Mac is required. The design was validated through usability sessions and focuses on meeting the developer at the right moment with minimal configuration.
JetBrains GameDev Day 2026 is scheduled for September 28 as a free online event for people building games, engines, tools, and production pipelines. The program covers Unity, Unreal Engine, Godot, proprietary engines, and engine-neutral infrastructure, with sessions on AI-assisted Figma-to-Unity integration, procedural content generation, ECS migration, cross-runtime C# and C++ debugging, Unreal performance profiling, and CI troubleshooting. The livestream starts at 10:00 am UTC, and recordings will be available on demand afterward; the full schedule and speaker details are still forthcoming. Watch parties are planned in Belgrade, alongside DevGAMM x FTW! attendee check-in, and at the JetBrains office in Limassol, with separate local timings and registration requirements.
TeamCity 2026.2 makes pipelines generally available on TeamCity Cloud and On-Premises, moving them beyond the Early Access Program and adding branch-aware editing, failure-tolerant job execution, promotion, job debugging, and VCS-unbound workflows. The release also expands AI capabilities: AI Assistant supports Bring Your Own Key for Anthropic, OpenAI, Google Gemini, other supported models, or a local LLM, while MCP adds pipeline management tools and OAuth/PKCE authorization. Additional changes include configurable retries for failed dependencies, IDEA plugin improvements, GitHub pull-request matching by source branch, and a choice of server- or agent-side Kotlin DSL compilation. The pipeline MCP post and delete tools require manually enabled Brave mode, and DSL compilation on agents is described as less restricting and more secure but subject to trade-offs. Bug-fix updates 2025.11.8 and 2026.1.4 also ship.
Static CI/CD credentials can leak through logs or artifacts, expose uncertainty over who copies them, and require rotation, so the article presents OIDC as an alternative for authenticating TeamCity builds. It explains the workload flow: an identity provider issues a signed JWT whose claims include validity, audience, and issuer, while the consuming service retrieves metadata and JWKS, verifies the signature, and checks those claims. The TeamCity OIDC JWT plugin makes the server an identity provider, supports RSA- or ECDSA-based signing, key rotation, configurable public issuer hosting, and extensions for HSMs or key-management services. After installation from JetBrains Marketplace, build configurations can issue tokens at startup or on demand, with default or fixed five-minute lifetimes, for direct presentation or token exchange with AWS, Google Cloud, and other OIDC services.
The best engineering reads, once a week.
