SonarScan fails for svn repository (Jenkins)

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.