Hi devs,
Currently our quality gate on sonarcloud is: no blocker issues on new code.
However there are 2 topics to discuss:
-
Sonarqube doesn’t use the concept of blocker issues anymore. They now have High, Medium, Low. Their mapping is defined at Issues (High = the old blocker + critical)
-
They have introduced the concept of “Clean as you code” which they’re proposing to set up as a quality gate with the following rules:
I’m proposing to follow it (it’s on new code only), and to keep the 80% coverage and 3% duplicated lines proposed. Note that it’s always possible to set a rule as a false positive (in case that for some reason the test coverage is badly measured for example, hopefully that shouldn’t happen soon and if it does then we can review our rule).
WDYT?
If you’re worried, we could also decide to test this for 1 month and decide if we keep it or not after that test period.
Thanks
PS1: If you want to see all the High rules: SonarCloud
PS2: We currently have 3 high severity issues on new code for platform: SonarCloud
There’s also 1 in commons: SonarCloud
And 1 in rendering: SonarCloud