Usually, customers want to naturally associate a stage with a customer environment. This means our stages should be constructed with jobs that make sense to re-run together. A stage can contain one to many jobs and acts as a logical grouping of related jobs.Īn important component to understand is that Azure DevOps, out of the box, provide an easy way to rerun Pipelines at the stage level. A stage is required however, there is a default if one is not provided. Recapping from a previous post, a stage is: To follow along I am leveraging non-ADO code in from Azure IaC Flavors and YAML templates from TheYAMLPipelineOne Stages Additionally, to assist with templating we will cover one way to leverage YAML objects which is a key tool when templating up and keeping your pipelines DRY (Don’t Repeat Yourself). It is now time to move towards stage templates. John Folberth continues his series on Azure DevOps Pipelines, by Leveraging Stages with YAML Objects.īy now we’ve covered the basics on tasks, jobs, stages, environments, variables and templates for jobs and tasks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |