SQ 7.9.1 Autodetection did not work when added sonar.scm.provider=tfvc

SonarQube Server / Community Build
1

Hello,
I have the problem in autodetecton of sonar.scm.provider although I did download the plugin and configured the project properties with the below values:

sonar.scm.provider=tfvc
sonar.tfvc.collectionuri=http://srv-dev-tfsxxxx:8080

Also i did try it from administration>configuration>SCM
but it is the same error as below:

SCM provider autodetection failed. Please use “sonar.scm.provider” to define SCM of your project, or disable the SCM Sensor in the project settings.

Can anyone help to solve this error.

2

Hi,

Welcome to the community!

In fact, you can consider that parameter vestigial. If all the pieces are in place, it’s entirely unneeded. So the real question here is why aren’t the pieces in place for analysis to automatically pick up on your SCM data?

How do you check out the project? Do you analyze from that root, checkout directory, or cd down into the project before analysis?

 
Ann

3

Hi Ann,

Thanks for your follow up. To analyze the project I created the project ID then in the TFS build I invoked the msbuild twice each time with one of the below parameters:

D:\sonar-scanner-msbuild-4.6.2.2108-net46\SonarScanner.MSBuild.exe

begin /k:“WebAll” /d:sonar.host.url=“http://xxxx/sonar” /d:sonar.login=“xxxxxxxxxxxxxxxxxx”

end /d:sonar.login=“xxxxxxxxxxxxxxxxxxxxxxx”

Would you please explain more what I need to do to put the pieces in place for analysis to automatically . Thanks for your support.

5

Hi,

This message appear if the property hasn’t been found. Where do you set it ?

Thank you.

9

Hi,
I set them to sonar-project.properties

Thank you

10

Could you please send us the full log of the analysis, in debug mode, so we can check wether the properties are well read.

Thank you.

11

Hi,
The problem solved when I added (sonar.scm.provider=tfvc) into [sonar-scanner-msbuild directory]\ sonar-scanner.properties.

Thanks for your support.