Introduction Azure DevOps Pipelines can be very powerful, even more so when coupled with Multi-Stage Pipelines. If new to this check out my post on
Background One of benefits on leveraging YAML based pipelines in Azure DevOps (ADO), is the ability for builds and deployments to be managed as code.
Disclaimer: This is more technical than what I like putting in a blog post. I don’t know a way around it as feel like it’s
This holiday season I decided to embark on a challenge of committing things back to the open source community. There already is the well-established Advent
Advanced usage of YAML Objects to automate the Azure DevOps Multi Stage Pipeline process.
One of the requested features of YAML DevOps Pipelines has been the ability to add a manual intervention task. One that may pause the pipeline
YAML Pipelines can be problematic to troubleshoot. Try PowerShell or downloading the logs for expanded template information!
YAML Pipelines can be optimized for reuse via templating at the task, job, and stage level.
MultiStage Pipelines can make deployments much much easier. Be sure to check out my previous post an overview of YAML Pipelines in Azure DevOps A
One of the announcements made by the Azure DevOps team that has gone under the radar is that of the ability to use YAML Pipelines