i am looking for interesting inputs concerning the design of Qualityprofiles. (And sorry for the coming wall of text ) My concern is the following:
What is a better way for me to separate the display of “a projects quality” (in sq-server) from the display of “things to work on” (in project-synced sonarlint)? (think: assessing different “dimensions” of quality)
I am currently assessing the quality of one codebase in three profiles in SQ. I named these profiles “buildbreaker”, “fixit” and “kitchensink”.
is used to check the minimal baseline (aka Qualitygate for build pipelines) a.k.a. “Must have”
is used to advise developers via sonarlint sync as to which findings are (in addition to buildbeaker) fix-worthy a.k.a. “Nice to have and encouraged to work on”
is used to be a boyscout radar to see what things possible are available to inspect
that if i also want to to keep a picture of changes over time, i cannot configure the same project with different profiles to see the different results
checking the same sq-project with different profiles would probably make the sonarlint-sync rather hectic (which would make devs rather mad )
After all, configuring this three different projects to get different results is a bit more hassle, but not a real bummer. The real culprit is that this way of doing things leads to a tripled sourcecode-linecount in the Administration/System view.
I would like to find a way to get the mentioned profiles different information but only count source-lines once, not thrice as the source-line-count-amount defines the amount of $$$ to hand over for moar features to sonarsource in DE or EE (Developer Edition / Enterprise Edition).
I currently work with the CE (Community Edition) so that is no concern, yet … but what if i would like to switch?
Maybe someone had this problem already? Or someone maybe has consulted ppl and might be able to chime in with some drops of knowledge? Or the solution is an easy one i just cannot envision?
Thank you for reading this far and TIA for any input at all!