TeamCity

Modern CI/CD Management
in TeamCity
EAP

Build smarter. Automate faster.

TeamCity Pipelines brings a new way to define and manage your build processes that is more visual, more flexible, and more future-ready. This new editor is available from version 2025.07.

Request access

What are pipelines?

Version 2025.07 and higher

Pipelines are a new way to define CI/CD workflows in TeamCity. Instead of maintaining multiple separate build configurations, you can now create a single pipeline that encapsulates your entire process – from build to deployment – in a clean and unified way.

Under the hood, it's still the same powerful TeamCity you trust, running familiar build chains and builds. But now it comes refreshed with a simplified user experience and modern tooling.

Why use pipelines?

Streamlined workflow definition

Combine related build steps into a single pipeline

Visual editor

Easily design and update pipelines using our intuitive drag-and-drop interface.

YAML support

Prefer code? Define pipelines in YAML format and store them in your repository.

Full interoperability

Switch between the visual editor and YAML anytime: they're fully synchronized.

Version-aware pipelines

TeamCity uses the version of the pipeline stored in the same revision you're building, even across branches.

What can pipelines handle today?

Pipelines are perfect for self-contained projects where all builds are always executed together.

Currently, pipelines:

Run as a full unit (step by step).
Don’t yet support selective step triggering (e.g. the ability to skip individual tasks).
Are ideal for workflows with less than 20 jobs.

Request access

Future plans 🚀

Starting from 2025.11

Adding pipelines to TeamCity is a key part of our long-term plan to make TeamCity more intuitive and user-friendly.

Our future plans for pipelines include:

Supporting snapshot dependencies between pipelines and regular build configurations.
Expanding support for build runners, triggers, features, and more.
Adding Kotlin DSL support.