Teamcity - Ability to connnect existing build configurations to pipelines

Created April 24, 2026 04:52

I was playing around with new pipeline feature in teamcity and while it's easier to view, it lacks the needed build step complexity.

I suggest adding an ability to attach existing build steps to the pipeline

This also allows for easier migrations from old build configuration, keeps plugin support and allows users to reuse saved templates/recipes

1 comment

Eric Borchardt

Created April 28, 2026 00:55

Thanks for the suggestion. What you're describing, reusing existing build steps inside pipeline jobs, is tracked across two open feature requests. The structural difference between pipelines and classic build configurations is intentional and documented in Pipelines vs Build Configurations and Chains. Adding composition primitives that let pipeline jobs reuse build steps is on the radar, though. I should also mention that Pipelines is still in early access and currently lacks some functionality, see Limitations and Special Notes.

The two existing requests that together cover what you described:

TW-89202: TeamCity/Pipelines reusable action. This is the closest match to your ask. It would add a composition primitive to pipelines, equivalent to meta-runners or recipes for classic build configurations, so a sequence of build steps could be defined once and reused across pipeline jobs.
TW-100301: Support any runners and features in jobs in yaml-only format. Today pipeline jobs only support Maven, Gradle, Node.js, and Script runners. This would extend pipeline jobs to use the full set of TeamCity runners and build features, which is the other half of the "build step complexity" you mentioned.

Please share your interest by voting for the feature requests above. Comments on YouTrack issues reach the development team directly, and this information is used to determine which features to include in future releases. Your feedback there is important to us!

Please sign in to leave a comment.