SonarScan fails for svn repository (Jenkins)

Make sure to tell us:

  • What version are you upgrading from? - 8.9.3
  • System information (Operating system, Java version, Database provider/version)
    Windows , JAVA - 17 , Database provider - SQL 14
  • What’s the issue you’re facing?
    Previously we had a project which has scan results of svn repository (through Jenkins pipeline) . Three repositories in svn were pushing scan results in one project in SonarQube(three different pipelines in Jenkins).
    After , sonarQube upgrade , one Jenkins pipeline successful , other two are failing with below error (previously all were successful)
    One which is successful , was defined before the other two which are failing.

EXECUTION FAILURE
INFO: ------------------------------------------------------------------------
INFO: Total time: 43.408s
INFO: Final Memory: 42M/147M
INFO: ------------------------------------------------------------------------
ERROR: Error during SonarScanner execution
java.lang.IllegalStateException: Authentication error when executing blame for file XXXX/SQL Files/XXXXX.sql

In previous version , we had a configuration to specify svn repo link l. which is not available now as it scan identifying .svn folder .

Hey there.

Were you previously configuring SVN information in the Web UI (under your project administration / settings).

There was a change to this behavior in SonarQube v9.1

You can find the analysis parameters to pass to the scanner in the documentation on SVN integration.

I’m not familiar with any setting that allowed you to point to a specific SVN repo – maybe you can shed some light on what you mean by that.

Release 9.1 upgrade notes

Secured settings no longer available in web services and on the scanner side
This change especially affects the analysis of SVN projects but also, possibly, the use of some 3rd-party plugins. Secured settings required to perform the analysis now need to be passed to the scanner as parameters.