Sonarqube extension upgrade to version 6 is not working , getting error as No agent found in pool

SonarQube Server / Community Build
, , ,
1

Sonarqube plugin version 5 ( Installed from marketplace )was working fine with azure devops . After the upgrade of sonarqube version to 6 , pipeline fails as No agent found in pool Default which satisfies the specified demands: maven Agent.Version -gtVersion 3.218.0
We are using self -hosted agent and its used by multiple projects , agent version upgrade will impact other projects.
1.Is there any way I can used old version which Sonarqube version 5 .
2.Can we disable this automatic upgrade of sonarqube.
3.We are using classic pipeline ,changing the version inside the task will work or do we need to install the new plugin/extension from marketplace again.
Please help me in solving this issue

2

Hey there.

You can continue to use v5 of the tasks just by swapping out SonarQubePrepare@6 or SonarQubeAnalyze@6 for SonarQubePrepare@5 and SonarQubePrepare@6. v5 have the same old agent demands.

You can find the old release VSIX here: Releases · SonarSource/sonar-scanner-azdo · GitHub

No, the auto-upgrade of extensions is an annoying Azure DevOps feature.

Yes, using the old version of the task will have the same old demands.

3

Hi @Priya26, and welcome to the community.

As of version 6, the extension requires that agents are at least at version 3.128.0.
If you do not have this version yet, you can still use the @5 tasks that require version 2.144.0.

They have been deprecated (which means they will be retired in a few months), but that should give you time to upgrade your agents.

Denis

6

Hi ,
Thanks for your reply . I am using prepare analysis task for sonarqube , when i change the version to 5 task is getting skipped.

7

That’s weird. I would be interested to see your Azure DevOps Pipeline YML and the logs from a build where the tasks are being skipped!

8

Hi Team,
Thanks for your assistance. Sonarqube task is running fine with version 5.
May i know when the version 5 will get retire so that accordingly we can update our build agents.

9

It will be a long time from now (no date defined, but not this year), and a warning will be visible ahead of time.

For context, v4.x of the tasks are still available, and v5.x was released several years ago.