Hey. It is called "Classic" because it was the only option available until the YAML Pipelines have been released more recently. Both are fully supported and will still be, there is no plan to deprecate any of them. The Classic (aka UI-made) pipelines are easier to start with and provide a graphical way to visualize the flow, while the YAML ones (aka code-based) provide a way to store your CICD definitions in code (with all the advantages deriving from that) and are more flexible, if you will.
Your 3 points are correct, to summarize and extend:
Classic Pipelines are of type Build (for CI) and Release (for CD)
YAML Pipelines are unified (multi-stage) so they can be used for CI, CD, and/or CICD
all the following are supported:
Build
Deploy
Classic (Build)
Classic (Release)
Classic (Build)
YAML
YAML
Classic (Release)
YAML
YAML
This is to say you can concatenate different ways.
While Classic and YAML are mostly at feature parity, there is no plan to make Environments work in Classic. And this is partially because in Classic Release you can define your stages (aka steps) visually and those somehow represent your environments. But it is true that you lose some logs and info in that way, which are otherwise available in Environments.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey. It is called "Classic" because it was the only option available until the YAML Pipelines have been released more recently. Both are fully supported and will still be, there is no plan to deprecate any of them. The Classic (aka UI-made) pipelines are easier to start with and provide a graphical way to visualize the flow, while the YAML ones (aka code-based) provide a way to store your CICD definitions in code (with all the advantages deriving from that) and are more flexible, if you will.
Your 3 points are correct, to summarize and extend:
This is to say you can concatenate different ways.
While Classic and YAML are mostly at feature parity, there is no plan to make Environments work in Classic. And this is partially because in Classic Release you can define your stages (aka steps) visually and those somehow represent your environments. But it is true that you lose some logs and info in that way, which are otherwise available in Environments.