SonarScanner for Azure DevOps latest(4.17) still run with Scanner version 4.4.0 for Charp application:
- versions used (SonarQube 7.9.4, Scanner for Azure DevOps 4.17)
- error observed (The Azure extension while analysis uses Sonar Scanner version 4.4.0. But in release notes of Scanner for Azure DevOps 4.17 say : ‘Bumped SonarScanner for .NET version 5.0.4’.
We need the use SonarScanner for .NET version 5.0.4 in Azure pipeline as it has removed the requirement of GUID from csproj and sln file.
Main issue to use the Scanner for Azure DevOps 4.17 in our application is that it skips the project where GUID is not present in .csproj file.
Reproduce issue: Analyze the csharp application which has multiple .csproj(with no GUIG´d in this file) in an Azure DevOps pipeline
Please find the below snapshot with the issue:
Are you hosting the build agent yourself ?
Thank you for the reply
No, We are currently using Azure Hosted Agents.
Thanks. Can you check that the Prepare Analysis Configuration task is also on 4.17.0 version when it has been run ?
Seems weird that an old version of the task is taken into account, this is not expected as we ship the corrent version on our side.
Maybe it can be worth to uninstall the extension, and reinstall it just after.
No it seems that the Prepare analysis stage have 4.13.0 version of Scanner for Azure DevOps.
Ok so i suggest you to uninstall / reinstall the extension itself, looks like something is not working correctly on Azure DevOps side.
Okay, Mickeal. Thank you for the support. I have just update the extension and tried. This is now working fine with 4.17.0 version in prepare and analyze stage both.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.