i’ve some problem with the autoassignment of the new issues to the svn committer.
- Community Edition Version 10.1 (build 73245)
- AWS Bitnami configuration (Linux Debian wihtout docker)
- Login through LDAP
The launch of the analysis is made through the maven plugin:
call mvn sonar:sonar -Dsonar.projectName=xxxxx -Dsonar.projectKey=xxxxx -Dsonar.host.url=xxxxx -Dsonar.token=xxxxxx -Dsonar.svn.username=xxxxx -Dsonar.svn.password.secured=xxxx -Dsonar.sourceEncoding=UTF-8 -Dsvnkit.http.spoolDirectory=../spool
I’ve created a test class with some Sonar issues to test and as a result I’m able to see the issues in the new code section but the issues have no assignee (an example on the image):
If I look at the suorce code of the file I see the correct blame information (the hidden name is correct):
The name showed is the login name of the svn account. The email address of the LDAP account is the same of the one of the SVN user.
In the sonar database table “users” i see in the column “login” a login in the format “name-surname-1234” (which is not the SVN login) and I see in the columns “external login” and “external_id” the value in the format “j.sparrow” (first letter of the name “.” and the surname) which is the SVN login.
In the previous versione of Sonar I’ve been using (9.xx) it worked well and at memory the configuration was equal.
Any possible idea on how to find some hints on the problem ? In the logs there not seems to be anything related. And everything seems to be working fine.