SonarQube 8.6.0.39681 SonarScanner for MSBuild 5.0.4 NOTE: This warning does not appear for the full build. Just the PR builds. Originally I get this warning in SonarQube: SCM provider autodetection failed. Please use "sonar.scm.provider" to define SCM of your project, or disable the SCM Sensor in the project settings. In order to fix this error I set the ‘sonar.scm.provider=git’. But then I get the error: Not inside a Git work tree: D:\a\1\s To fix that I have tried to set the ‘sonar.projectBaseDir’ but I cannot find the format to set. If I use $(Build.SourcesDirectory) the build fails with: [error]java.nio.file.InvalidPathException: Illegal char at index 2: 'D:\a\1\s\' I have tried many different formats… D:\a\1\s\My.Repo.Dir at index 2: 'D:\a\1\s\' … or … [error]java.lang.IllegalStateException: Error when resolving baseDir What format should baseDir take? Is there a way to use the Windows paths and not get the error? Basically, what am I doing wrong and how do I fix it?

Hi, You shouldn’t need to set sonar.projectBaseDir. It’s only needed in unusual situation. Generally you should kick analysis off from the project root directory, which will naturally put you in the directory where analysis expects to find the SCM data. Also generally, if analysis doesn’t automatically detect your SCM flavor &etc, then manually setting a flavor with sonar.scm.provider isn’t going to help. TBH, I’m not sure it ever did, & we should re-visit that advice. (I’ll be referring that internally.) So. This started from SCM provider autodetection failed. If we back up to that, then the question is why autodetection failed. Are you analyzing from project root, or do you cd down in the structure before kicking off analysis? Ann

If we’re going to “back up to the start” it started with this error in my PR builds: Could not find ref ‘‘refs/heads/development’’ in refs/heads, refs/remotes/upstream or refs/remotes/origin. You may see unexpected issues and changes. Please make sure to fetch this ref before pull request analysis. So, I added a checkout of the root branch to the pipeline. Then I started getting the SCM error. So I added that. Then I got the error I posted here. I don’t explicitly change the directory, no. I added Get-Location calls between tasks and don’t see any change all the way through the pipeline.

Hi, These may be helpful: [image] Gitlab Merge Request: Could not find ref: dev in refs/heads, refs/remotes/upstream or refs/remotes/origin SonarCloud Error message: Could not find ref: dev in refs/heads, refs/remotes/upstream or refs/remotes/origin This results in failure to compute coverage for our merge requests within gitlab. We have already set up the depth to a 1000 without success. sonarqube: image: name: sonarsource/sonar-scanner-cli:latest entrypoint: [""] stage: Deploy tags: - gamma - dind variables: SONAR_USER_HOME: "${CI_PROJECT_DIR}/.sonar" GIT_DEPTH: "1000" cache: key: ${CI_JOB_NAME} paths: … [image] Could not find ref 'refs/heads/master' in refs/heads, refs/remotes/upstream or refs/remotes/origin SonarQube Hi, I’m getting the warning below when running SonarQube from within a Docker-container using Azure DevOps. Could not find ref ‘refs/heads/master’ in refs/heads, refs/remotes/upstream or refs/remotes/origin You may see unexpected issues and changes. Please make sure to fetch this ref before pull request analysis. When building the Docker container I pass the arguments at build time docker build \ --build-arg sq_pr_branch=/d:sonar.pullrequest.branch=refs/heads/ \ --build-arg sq… [image] Could not find ref 'develop/v8.14.0' in refs/heads, refs/remotes/upstream or refs/remotes/origin. You may see unexpected issues and changes. Please make sure to fetch this ref before pull request analysis SonarQube which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension) SonarQube => 8.4.2 Sonar Scanner => 4.10.0.19059 Teamcity => 2020.1.5 what are you trying to achieve? I’m trying to achieve pull request analysis what have you tried so far to achieve this I have configured the build steps in TeamCity and performing the analysis The Pull request analysis is showing 0 issues(for all PRs) even though it is having issues. Warning showing is “Could not find ref ‘develop/v8.… Ann

Thanks but I didn’t find anything in those. They looked like they were unfixed as well. That said I have tried a few things and cannot change the Pipeline.Workspace at all. In fact I’ve gotten an error that said Pipeline.Workspace cannot be changed. So, it looks like the only way to change the working directory is within the task itself. I have no idea how to change the current directory. Should I run the analysis from a powershell task? That would allow me to set the workingDirectory.

Hi, This [image] padillah: Could not find ref ‘‘refs/heads/development’’ in refs/heads, refs/remotes/upstream or refs/remotes/origin. You may see unexpected issues and changes. Please make sure to fetch this ref before pull request analysis. is about the scanner not being able to find in your SCM what you’ve asked it to analyze. Often this is caused by your CI auto/“helpfully” doing a merge commit on the PR early in the process. Ann

Thank you, that is interesting. Currently I’m passing sonar.pullrequest.base='refs/heads/development' … and … sonar.pullrequest.branch='refs/heads/Feature/changedBranch' Should I modify this? Or is there a way to get Azure to not merge commit until a certain point?

What value do I use for sonar.projectBaseDir?

SonarQube Server / Community Build

ganncamp (G Ann Campbell) January 29, 2021, 7:28pm 5

Hi,

These may be helpful:

Ann

Topic		Replies	Views
Sonnar scanner using wrong base dir SonarQube Cloud	4	891	August 3, 2023
sonar.projectBaseDir doesn't work SonarQube Server / Community Build	5	921	April 27, 2023
Azure DevOps SonarQube Buildstep Plugin needs adaptable projectBaseDir when using MSBuild SonarQube Server / Community Build scanner , dotnet	1	570	November 1, 2023
Wrong "Base Dir" for SonarCloud analyze task (randomly) SonarQube Cloud coverage , dotnet	5	754	March 19, 2024
SonarQubePrepare@7 Azure DevOps Task not reading sonar.projectBaseDir SonarQube Server / Community Build dotnet	16	2710	March 12, 2025

What value do I use for sonar.projectBaseDir?

Related topics