Error in SonarQube when launching svn blame

Question

I recently upgraded my SonarQube server from 4.5.2 to 5.0.1, then to 5.1 (see edit below).

Suddenly, the analysis of a multi-module Maven project failed with the fol

Answer 1

I had this problem and it was caused by not having an active installation of SVN on the build machine that was running the sonar analysis. It doesn't matter what the sonar box has installed. It's the build agent which needs to do the SVN blame.

I was using CentOS. The magic was

sudo yum install svn

The final trick was to make sure that the build machine was using the same version of SVN for checkout as the version I installed. If the build machine was natively using a different version you may have to make sure it cleans the whole workspace before its next check out too.

Finally, don't forget that Sonar needs your SVN credentials too!

Answer 2

Please check that the SonarQube process has the same enviroment variables, as you are using for testing.

Answer 3

This issue can be solve by two way,
1. by setting the sonar.properties -Dsonar.scm.disabled=True, this is valid only for sonarrunner.bat sonar analysis,
2. If your doing using any other type analysis then login with admin default admin is admin/admin(username/password).http://yourDomin:port/settings/index(e.g http://localhost:9000/settings/index) then in category select the scm and disable the scm sensor set as true.
3.or else u can add the svn plugin to the sonar http://your_domain:port/updatecenter/available after login as admin(admin/admin), search for the available plugin and select the svn and install it..

Answer 4

I experienced same issue after installing SonarQube 5.1, go to Update Center:

http://your_domain:port/updatecenter/available

search for the "SVN", click "Install"

https://docs.sonarqube.org/display/PLUG/SVN+Plugin

Something like this will appear:

SonarQube needs to be restarted in order to install the following plugins: sonar-scm-svn-plugin-1.0.jar

Restart your SonarQube.

Answer 5

use the below command which will disable the svn related issues

-Dsonar.scm.disabled=True

this will disable the svn

Answer 6

I have just installed SonarQube 5.0.1 on a Redhat Linux machine and I have exactly the same problem.

Instead of disabling the scm stats plugin, I have installed a svn client (svnkit.x86_64) and the build is executed successfully with SCM activated. So I guess on Windows, you should install a svn client and put it on the PATH.