Inaccurate Code Coverage Reporting in Pull Requests

[Claire_Villard]

Thanks @Prasad_Dodla

There is a similar thread where the user found the solution for themselves, having the same issue as you:

SCM provider autodetection failed for Azure Devops pipeline

In the hope that the forum may be useful to some - the issue here was that the analysis was being performed at the wrong level when source code was checked out into the Azure DevOps pipeline. The issue was seen in the pull-request where the path prefix was wrong (not sure why as it was working previously): [sonar-issue-blur] By setting sonar.projectBaseDir on the SonarCloudPrepare task to the Azure DevOps pipeline variable Build.SourcesDirectory the warning in the analysis run went away and …

Could you try this solution?
Claire