Skip to main content

Azure DevOps - Agent Auto-provisioning

When you create a new Agent Pool in Azure DevOps, you get the following options that can be selected:

  • Auto-provision corresponding agent pools in all projects
  • Allow all pipelines to use this pool

 

The second option is kind-of self explaining but what does the first option do?

What’s important to understand is that an agent pool exists at multiple levels, you have one at the organization level and you have one at the project level. The project level pool is not really a new pool but rather an import of the organization level agent pool into your team project. Your Azure pipelines will always target the project level pool.

By selecting the ‘Auto-provision corresponding agent pools in all projects’ checkbox(which is checked by default) the organization agent pool is imported in all your team projects and is accessible there immediately. If you didn’t set this checkbox, you have to import the organization agent pool yourself.

Therefore go to Project Settings > Agent Pools and click on New Agent Pool…

If you select here the ‘Base it on an existing organization agent pool’ option you can import the organization queue yourself.

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’: ...