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 optimized for reuse via templating at the task, job, and stage level.
I know I am an advocate for YAML Pipelines to handle builds and releases; however, that doesn’t mean can’t take a minute to emphasis the
For those that are unfamiliar Azure Data Factory is defined as: …the cloud-based ETL and data integration service that allows you to create data-driven workflows for
One thing I continuously see is a discrepancy on how to name Azure resources. I’ve seen such usage as just ‘Program1’ and have that name
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 benefits of leveraging and automating ARM templates is the ability to apply a standard naming convention. Using the Cloud Adoption Framework’s as
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