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
SonarQube: Switch scanner version for .NET framework within azure devops SonarQube Server / Community Build csharp , sonarqube , scanner , azuredevops-services	4	2338	February 7, 2021
Scanner for .NET 9.0.1 Sonar Updates sonarqube , scanner , dotnet , azure-devops , sonarqube-cloud	0	58	October 25, 2024
SonarQube causing build errors in .NET 6 project in Azure Pipelines SonarQube Server / Community Build scanner , dotnet	6	1673	May 12, 2022
SonarScanner does not support .NET 6.0 (LTS) sdk/runtime SonarQube Cloud csharp , scanner , azuredevops-services , dotnet	15	11967	December 1, 2021
ADO sonar task version 7, unexpected issues SonarQube Server / Community Build sonarqube , scanner , dotnet	1	44	January 17, 2025

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

Related topics