Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Please explain why YAML pipelines are the default vs Classic #5114
The YAML pipelines flow is substandard in every way to the Classic flow. Classic is simpler, easier to setup, doesn't require me to write and test and debug a text file, and covers 99.99% of use cases, yet it is seemingly being sidelined in favour of YAML - why? What benefit(s) does YAML give over Classic, apart from the fact that you can version YAML (but you could probably implement pipeline versioning into Classic anyway)? How do I setup separate Build and Release pipelines in the YAML flow?
It seems that YAML pipelines were introduced as the Next Big Thing and made default without any consideration for those who are used to the Classic flow. If you want YAML to succeed and more importantly, for Classic users to migrate to it, you absolutely need a walkthrough document that takes a project with Classic build and release pipelines, and converts them it to the
Furthermore, why are Release pipelines not being pushed to use a YAML file?
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
As you mentioned YAML have the advantage of being part of your source code. In addition to that it's just a text file that I can more easily share with my team, or write about in blog posts.
I think it's good YAML will become the standard but I agree that Microsoft may be jumping the gun here. For YAML to become the standard, the visual building interface and functionality should exceed Classic.
In my opinion YAML is very much a viable replacement now (since a few months back). Just doing "normal" devops stuff and multistage pipelines works great for both build and release (database, frontend and backend).