Hi, we are currently using the SonarQube extension for Azure DevOps version 5 on Azure agents in Windows and looking to upgrade our pipeline to use version 6. Unfortunately SonarQubePrepare@6 step downloads always the classic (.NET Framework) Sonar scanner while we use .NET6 / .NET8 which leads to …

As mentioned in the thread that was split from this one, I found our issue. It appears we have a task that removed the working directory in order to have a clean Code coverage result. Since the scanner is downloaded in the Sonar task since version 6 it was removed with the working directory and thus…

Select dotnet instead of classic scanner in SonarQubePrepare@6 (Azure DevOps) for Windows agent

SonarQube Server / Community Build

Colin (Colin) Split this topic June 18, 2024, 8:36am 12

A post was split to a new topic: Issue with CLI Scanner and v6 of Azure DevOps Tasks

Topic		Replies	Views
SonarScanner does not support .NET 6.0 (LTS) sdk/runtime SonarQube Cloud csharp , scanner , azuredevops-services , dotnet	15	12045	December 1, 2021
How do you specify the sonarscanner version that is being used with SonarQubeAnalyze task? SonarQube Server / Community Build sonarqube , scanner , azuredevops-services , azuredevops-server , azure-devops	10	2672	December 12, 2022
SonarQube: Switch scanner version for .NET framework within azure devops SonarQube Server / Community Build csharp , sonarqube , scanner , azuredevops-services	4	2371	February 7, 2021
SonarQube as support .NET6 scanner SonarQube Server / Community Build sonarqube , scanner	2	235	June 20, 2023
Deploy pipeline without using scanner-mode MsBuild SonarQube Server / Community Build scanner , dotnet , pipeline , azure-devops	12	1156	August 29, 2023

Select dotnet instead of classic scanner in SonarQubePrepare@6 (Azure DevOps) for Windows agent

Related topics