Skip to main content

Azure DevOps–Update to the v3.x build agents

A colleague trying to add SonarQube integration to his build pipeline in Azure DevOps, contacted me because he got an error in his build pipeline.

This is the error he got:

##[error]No agent found in pool default which satisfies the following demand: Agent.Version. All demands: msbuild, visualstudio, Agent.Version -gtVersion 3.218.0

The problem was caused by the SonarQubePrepare task he just added to his build pipeline:

It still worked with an older SonarQubePrepare version however the task is marked as deprecated:

##[warning]This task is deprecated. Please upgrade to the latest version. For more information, refer to https://docs.sonarsource.com/sonarqube/latest/analyzing-source-code/scanners/sonarqube-extension-for-azure-devops/

Updating a build agent

I thought the fix would be easy; just update the outdated build agent(s).

  • Therefore go to Project Settings –> Agent Pools.
  • Click on the Agent pool which contains the agent you want to update: 
  • On the detail screen, click on Update All Agents:

  • Or go to the Agents tab, click on the 3 dots next to the agent and choose Update Agent:

Remark: The screenshots above are taken after successfully upgrading the agent. So they already refer to the v3.x. version.

Unfortunately in this case it didn’t help and the agent remained on v2.x. A look at the documentation brought me a step closer to a solution. The v3.x version of the agent were part of a newer Azure DevOps Server version. 

Time for an upgrade!

After upgrading the Azure DevOps server instance, I returned to the Agent Pool details and clicked on Update All Agents again. And this time the build agent upgrade was finally triggered:

Hurray!

More information

SonarQube extension for Azure DevOps (sonarsource.com)

Agent software version 3 - Azure Pipelines | Microsoft Learn

Labels:

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         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

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.
Read more