New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Convert from visual designer to YAML #2504
Comments
Export the yaml from the visual designer using view yaml (on the far right of the edit screen) copy the yaml and then paste that into a new file in the root of the git repository with name azure-pipeline.yml |
Is it also possible to convert release-pipelines, initially developed using the visual designer, to yaml, and keep this separate from the build-pipeline? |
You can deploy from a YAML pipeline; some of our docs show examples of this. However, YAML pipelines don't have stages or approvals. |
For designer builds, the "view YAML" button is the best bet. As Andy said, we aren't quite there on feature parity for designer releases. |
Does anyone know where the "View YAML" button went? I can't see it on the far right of the edit screen, or anywhere else for that matter. |
@yannduran, open edit on the visual build pipeline and now for each step, select the step and you can see yam button right top. |
@RolfEleveld, oh I see. You only see the YAML step-by-step, not for the whole pipeline. Thanks! I was expecting something that allowed you to see the YAML for the whole pipeline. I mean you can export a whole pipeline to JSON, so it'd seem reasonable to expect that you could also see/export it to YAML, especially with the emphasis that's being placed on YAML now. |
It's available at the Job level. |
FYI soon will be possible to export an entire pipeline as YAML; |
…resh-get-started Security get started and refresh
I've been working with the visual designer for some time, but I read that we are encouraged to move to YAML. Is there a way to easily convert from visual designer to YAML?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: