I’m on vacation this week, so I’ve been eating fatty foods and drinking tasty beverages instead of looking after the fine features of Azure DevOps. But, of course, the DevOps community isn’t on vacation, so here’s some of the great news and stories that they’ve been working on this week.<\/p>\n
Containerised CI\/CD pipelines with Azure DevOps<\/a><\/strong> Using the same Azure DevOps build steps for Terraform with different Pipelines with Task Groups to build an Azure Linux SQL VM<\/a><\/strong> TFVC to Git \u2013 Things to Consider<\/a><\/strong> Azure DevOps Rest Api. 18. Create and Clone Build Definitions<\/a><\/strong>
\nIf you’re a regular reader of this top stories roundup, you’ll know that I can’t stop talking about containerizing<\/a> your CI\/CD process<\/a>. Brent Robinson has another great post about simplifying your builds and supporting complex architectures with containers.<\/p>\n
\nI love building out infrastructure automatically, scripting the configuration for automation and repeatability. Rob Sewell’s series of blog posts explains how to use Azure Pipelines and Terraform to create infrastructure like an Azure Linux SQL VM.<\/p>\n
\nCentralized version control makes a lot of sense for a lot of workflows and repositories. But if you’re only using it because of momentum, then you want to move into a distributed workflow, Chris Ayers has some good tips to get you ready for your move.<\/p>\n
\nOne of the great things about checking in your build definition as YAML is that you don’t need a build definition per branch; so it’s less common that you’ll need to clone them. But when you do, it’s helpful to be able to do that programmatically. Shamrai Alexander shows you how to use the REST API to clone build definitions.<\/p>\n