'Writing YAML VS using Visual Designer on Azure Devops
I am sort of new to azure devops and I had to build few builds and release pipelines.
I have done it with visual designer and it was smooth & easy, while using yaml is much more prone to mistakes.
If I work in a team that uses yaml , I do it in designer first and then copy the yaml.
Apart from saving to the repo automatically, why the pain ? why not just use the designer ?
Missing the obvious?
Solution 1:[1]
Because its not scalable, how do you manage hundreds of visual jobs? only by hand, yaml jobs can be mass edited, than can use templating\looping\if and so on, you can reuse them etc. I'd really wish they made yaml for releases, managing releases is a pain in Azure Devops right now, builds are easy. we've got yamls...
Solution 2:[2]
I had same issues with new yaml only way of doing things in DevOps. User should have a choice to switch between two. For script lovers, they can always copy the generated script and automate.
I stumbled upon (after lot of reading) the setting menu hidden on the yaml code generated. Click on the settings link and it open a details pane on the right of the page. Refer the attached image.
This is where you can provide additional details and settings value. Once saved, it reflected back in yaml script.
I hope this bridge the gap between two type of users. :)
Solution 3:[3]
You can always use the azuredevops api for managing tasks involving bulk build and releases. Not as clean as a yaml but still a json file that you can relatively easy modify export/import etc...
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | 4c74356b41 |
| Solution 2 | Sanjay Zalke |
| Solution 3 | seashells on azure |