Treasure Map for Azure DevOps at Scale: Azure Pipelines Part 2

Continuing our adventure focused on Azure Pipelines to manage our libraries on your Azure DevOps organization

Let’s continue our adventure focused on Azure Pipelines. And here, we talk about Libraries. But here, in my humble opinion, we need again to create a standardization, because we have the same problem as when we talk about Environments.

Library feature was delivered as a project-level functionality, and in many cases we have a pipeline process (stages and jobs) that applies to our entire organization!

There are a bunch of variables that we use on different projects and we have the same pipeline process by sharing YAML templates. Therefore we need to replicate these variables between all Team Projects.

Then to solve this problem always remember that you need:

• Process: define all Libraries to all Team Projects;
• Governance: Create controls and reports to ensure this standardization.

The example below shows how can validate all libraries in each of the team projects (click on link for more details):

• How to: Create Variable Groups (Libraries) Dashboard on Azure DevOps: report to extract lall team projects, variables inside your Azure DevOps organization

From there, we validate all team projects, thus verifying whether we have standardization in the creation of libraries.

Well, this was my ninth big clue for us to explore the world of Azure DevOps at Scale. See you in the next challenge!!!