SonarQube version: 6.7
Currently, we use above version and teams can use sonar.branch.name or sonar.branch. I know that sonar.branch will make a new project based on the branch also, which is a problem. And I know that 7.x will fail analysis if sonar.branch is used
Another problem is that teams can use a branch name in project key, or name etc.
I’m looking to put a stop to that, my proposed solution is to use a project permission template and using the pattern so that this won’t happen.
example, if a team tries to create a project like: 1234_new_sonarqube_project_master
I’d like to block that by using pattern maybe below:
Is this a reasonable idea or are there any problems in that?
I’ve tested the regex on: https://regex101.com/ and it works for above
I’d love to hear ideas or feedback/criticism
Hopefully we will move to 7.9 soon, but in the meantime I’d like to block project analysis like that