Skip to main content

Azure Pipelines–Variable groups

I'm currently migrating an existing CI/CD pipeline build in Azure DevOps from the ‘classic’ build approach to YAML templates.

One of the building blocks you can use in Azure Pipelines are variable groups. Variable groups allow you to create and store values and secrets that can be used in multiple pipelines.

Create a variable group

To create a variable group, go to your Azure DevOps project. Open the Pipelines section from the left menu and click on Library.

Here you can click on + Variable Group to create a new variable group.

Enter a name and a description for the group.

Now you can start adding any variable you want by clicking on the + Add.

Using a variable group inside your YAML pipeline

Using a variable group inside a YAML pipeline, is quite easy. You just need to add a reference to the group inside the variable section:

It is still possible to include other variables as well by using the name/value syntax:

Scoping a variable group to a stage

One of the things you can do with the ‘classic’ release pipeline, is linking a variable group to a stage in a release pipeline. By doing that the variables from the variable group get scoped to these stages and aren't accessible in the other stages of the same release.

In the YAML pipeline, you can achieve something similar by setting the variable group at the stage level:

 

More information: https://learn.microsoft.com/en-us/azure/devops/pipelines/library/variable-groups?view=azure-devops&tabs=yaml

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...