What's New in TeamCity 2026.2

General availability

TeamCity 2025.07 introduced pipelines as an Early Access Program (EAP) feature — instantly available on TeamCity Cloud, and on request for TeamCity On-Premises. Since then, we've been steadily closing the gap with classic build configurations, adding:

• Compatibility with familiar build features and steps

• Integration with build chains, so pipelines can slot into existing workflows

• Kotlin DSL support for configuration-as-code

• The Custom Build dialog, output parameters, and other familiar elements of build configurations

With this release, pipelines leave the EAP: they are now generally available on both TeamCity Cloud and On-Premises, for projects of any size and complexity.

Pipeline development does not stop here — see our roadmap for what's next.

Debug jobs

You can now test a single pipeline job without triggering the whole pipeline. Open a job's ellipsis menu and choose Debug — TeamCity runs just that job (and anything it depends on) with its current settings, complete with a live build log and terminal access to the agent that picked it up.

Learn more: Debug Jobs

Improved branch handling

Pipelines are now better equipped to work with feature branches: in edit mode, you can switch between different repository branches and design unique workflows for each of them.

In addition, TeamCity now handles protected branches correctly. An attempt to commit edits made in the UI to a protected branch now results in a clear warning, and a suggestion to save the updated .yml file to another branch.

Learn more: Feature Branches

Run through failures

When setting up job dependencies, you can now enable Run job even if upstream fails so a job keeps running even when the upstream job it depends on fails, instead of being automatically canceled.

The pipeline run is still marked as failed overall, but this lets you guarantee that specific jobs (for example, cleanup or notification steps) always run.

Learn more: Dependencies

Promote pipeline runs

Promote — the button that triggers the downstream part of a build chain from an older, already-finished build — now works for pipelines, not just build configurations.

For example, promote a successful "Build Docker image" run into the "Upload to DockerHub" configuration or pipeline to re-deploy that artifact without rebuilding it.

Learn more: Promote a build

Unbound pipelines

You can now create pipelines without VCS roots attached. Previously, this option was only available for build configurations. Choose the “Without repository” option when creating a pipeline to create a custom workflow that does not check out any remote sources.

Learn more: Create and Edit Pipelines

Amazon ECR support

Pipelines and jobs now show parent project Amazon ECR connections under their Integrations sections.

Currently, only inherited ECR integrations are supported — you cannot create local integrations via pipeline settings panel or YAML markup.

Learn more: Pipeline integrations

AI Assistant

Starting with TeamCity 2026.2, you're no longer limited to the built-in JetBrains AI: AI Assistant now supports "bring your own key" (BYOK), letting you connect it to a third-party AI provider your organization already has access to. Choose a provider under the Provider selector and enter your API key, and AI Assistant will run on that model instead. The bottom of the Assistant panel always shows which model is currently active.

In addition, AI Assistant now works with pipelines, not just classic build configurations, and ships with local documentation sources, making it more accurate and less prone to hallucinations.

Learn more: Providers

MCP improvements

TeamCity's MCP server now exposes three new tools for managing pipelines — retrieve, edit, or delete them straight from your AI agent. You can also connect using OAuth instead of pre-configuring a personal access token.

Learn more: TeamCity MCP.