SVN authentication failure when running a Sonar analysis in Jenkins 1.620 SonarQube 5.1.1

You can configure it on the SonarQube server:

Global: Settings → General → SCM → SVN

Per project: Settings → General Settings → SCM → SVN

In case it might help, here is an alternative way to do it based on this thread in a google group.

Mind you, it is certainly less secure than set the SVN user and pwd in SonarQube server, but it might help as a temporary workaround:

In the Jenkins job >> SonarQube Scanner Build Step >> Analysis Properties

Set the two properties below:

sonar.svn.username=<SVN USERNAME>
sonar.svn.password.secured=<SVN PASSWORD>

Note that the password is actually not secured at all, since it is not encrypted. Therefore a nice move is to set it in a password variable in Jenkins and to pass this variable in the sonar.svn.password.secured property value. This way it is, at least, not readable.

In 6.7.x ,you can find in Administration -> Configuration -> General Settings → SCM → SVN . But svn option can only be seen if you install svn plugin in market.