we use one Sonarqube Enterprise instance for a LOT of different projects.
One may set one default quality profile and one default quality gate, but this is no longer
sufficient when so many different projects are to be supported.
This means we have to use a lot of Sonarqube web api calls for provisioning a whole bag full of
different projects in our pipelines.
A comprehensive project template - instead of only a permission template - would be better.
This template may optionally contain all project settings, if a setting is not mentioned,
the default is taken, i.e.:
- new code definition
- main branch
- different quality profile for any language if not default
- different quality gate if not default
- activate/deactivate plugins, this would go hand in hand with the proposal of Alex
Restriction of the download of scanner plugins to those that are essentially needed - #3 by Alexandre_Gigleux
This template should be driven by project key (
sonar.projectKey) pattern (regexp),
similar to the permission templates - actually it would make permission templates obsolete.
Would be very helpful, if there was a validation when creating a new project template or
editing an exisiting one if there’s a possible regexp collision.
Of course, dealing with regexp requires a strict naming convention for project keys,
but I assume that everyone already uses one, otherwise it would be a mess.