I use SonarQube 8.3 Developer edition.
I am sure that many of my fellow peers use configuration files all the time. They are useful because they can be checked in to source control for audit-ability, they can be templated, they can live along side the project that they are configuring etc.
Sonar has a file called sonar-project.properties that allows you to configure a projectName and a select few other values.
Often when SonarSource releases a new feature I hope to see a config parameter for it but nearly always the only way to configure it is to use the Web UI. This is painful for me because only a small subset of users have project admin rights and even if I gave every developer admin rights i would then need to train them all on how to enable certain features and functionality and hope they don’t misconfigure other things.
If you do a quick search of the Community the message from SonarSource is pretty clear - How to set sonar.issue.ignore.block in sonar-project.properties
We recommend users to use the UI to configure this, for best experience. Consider the configuration via
sonar-project.propertiesas an undocumented hack, not official supported that may or may not work reliably, use at your own risk.
Some examples of things I would like to configure with sonar-project.properties:
- PR decoration. For every new project I have to go to the UI -> Project Settings -> General -> PR Decoration -> Choose config from dropdown and save
- Configuring the New Code period (see Why cant Code Period start from my main branch when scanning a feature branch?)
In summary, my question is do SonarSource favour the use of Web UI in order to configure projects? If yes, why - considering the advantages I listed above regarding file based configuration for the project? If no, how would you recommend solving for my two problems above?