sonarqubeorg.tmatesoft.svn.core.SVNAuthenticationException: svn: E170001: Authentication required for Repository'

[gordo...@gmail.com]

Hello,

We use sonarqube with jenkins and it is very useful.  Lately we get some odd authentication errors on new branches in the same svn repository when we use the svn blame function.  The same jobs run properly for existing branches.  From running the sonar-runner online it looks as though the user and password are getting passed in but the authentication fails for these new branches.  There is some svn authentication but it is all pretty global, the permissions are defined for all branches, not for specific ones. 

For the new branches we get the following errors:

ERROR: Error during SonarQube Scanner execution
java.lang.IllegalStateException: Error when executing blame for file
Caused by: org.tmatesoft.svn.core.SVNAuthenticationException: svn: E170001: Authentication required for  Repository'

Any advice would be appreciated,

Thank you,

Gordon

[G. Ann Campbell]

Hi Gordon,

This is on the SVN side rather than on the SonarQube side. The analysis is just reporting to you the error it got when trying to connect to SVN with your provided credentials.

HTH,

Ann

[Julien HENRY]

Hi Gordon,

This could be a bug in SVNKit, but to confirm, please try running the native svn command line tool in the exact same situation (svn blame xxx), and compare with SVNKit, using their command line tool (download it here: https://www.svnkit.com/org.tmatesoft.svn_1.9.0.standalone.zip).

++

Julien

[gordo...@gmail.com]

Hello,

If I run sonar-runner I get the error.  If I run the blame directly using jsvn from the svnkit I get what looks like reasonable xml output and no errors.  Is there something other than jsvn blame that I should test?

The sonar-runner also works consistently for other branches in the same repository.  Branches up to r9 (and there have been a lot of them) work, r10 and r11 don't.  I don't see anything different about the new branches, no odd characters in the names or anything.  The authentication is configured for the whole instance, there is nothing specific for these branches.

I haven't found anything useful in the subversion logs.

Thank you,

Gordon

[gordo...@gmail.com]

Hello,

The developer working on this item corrected me.  It is not failing for the branches in particular, it fails part way through.  Looks like it could be a timeout.  I'm looking at the configuration.

Thank you,

Gordon

On Tuesday, September 12, 2017 at 12:38:32 PM UTC-4, gordo...@gmail.com wrote: