Restrict Code Analysis from Personal Namespace in GitLab

We are using following technologies for our code analysis :
** SonarQube Community Edition Version 7.9.4 (build 35981)
** GitLab Enterprise Edition 12.8.10-ee
** Jenkins ver. 2.222.4

We are looking forward to restrict code scans/analysis for projects residing in personal namespaces in GitLab.

Is there any such provision available in SonarQube ?

Hi,

It’s not clear to me what you’re asking. You want to prevent analysis of certain projects? If so, that’s really outside of SonarQube. I guess you would look at your GitLab CI setup.

 
HTH,
Ann

In GitLab, projects are created inside namespace and a namespace is a unique name to be used as a user name, a group name, or a subgroup name.

  • http://gitlab.example.com/username
  • http://gitlab.example.com/groupname
  • http://gitlab.example.com/groupname/subgroup_name

We are looking forward to restrict the Code Analysis of projects which would exist inside user namespaces “http://gitlab.example.com/username

Is there any such provision available in any to the Editions of SonarQube if not in the Community Edition ?

Hi,

This isn’t about editions. Analysis is triggered not by SonarQube but outside it. So you need to look at controlling what triggers analysis.

 
:woman_shrugging:
Ann