- which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
SonarQube Enterprise Edition Version 8.2 (build 32929)
- what are you trying to achieve
Gitlab group synchronization to match strictly, not relatively.
Hi everyone, we are in the midst of evaluating the Sonarqube EE for our organization, in particular the group synchronization function with Gitlab.
Take for example a user “dev-A”, the account of a developer and “mnt-A”, the account of a maintainer. They are both placed in the following group:
“dev-A” is in group
“mnt-A” is in group
To allow the group synchronization to take place, I have also created both of that group in SonarQube. What happen is that when I log in to SonarQube with “dev-A”, user “dev-A” is being added into both of the groups (
users/team-A/maintainer ), what I wanted instead is that “dev-A” should only be added into group
I believe the relative hierarchy is doing something here and which leads to my question: is there any way to force the group mapping to match exactly as they are in Gitlab? E.g. user “dev-A” is in
users/team-A/maintainer/developer and therefore in Sonarqube, “dev-A” should only go into group
users/team-A/maintainer/developer, and not its “super” group