We added a Reliability Rating and set it to B to pass bugs that have a severity of ‘minor’. It does what it needs to do, but there is a message that says, ‘The quality gate used by this project does not comply with Clean as You Code.
How do we get rid of this message? This is critical on our side since we need to submit the result prior to our production deployment. The approver might question this message.
Then tell us:
Hi,
Unfortunately, the only way to get rid of that message in 9.9 is to change your Quality Gate to include only conditions on new code.
We’ve softened that considerably in current versions. If this is really important to you, I suggest you upgrade to the latest version, which is currently 10.5.1 (10.6 expected next week).
HTH,
Ann
Hi @ganncamp to understand, is this warning message now optional to choose or still always showing on the main overview page under “QUALITY GATE STATUS”?
“The quality gate used by this project does not comply with Clean as You Code.”
Hi @Mark_van_Osch,
I guess you’re asking if you can make the message go away? Only by changing your Quality Gate. Or by upgrading to a newer version, where the message has been softened a good bit.
HTH,
Ann
Yes, we are upgrading to the latest 10.6 very soon. But my question was what “softening a bit” then actually means?
Hi,
In 9.9 the warning was a bit overzealous, showing up for every project where the Quality Gate didn’t match exactly that version’s definition of Clean as You Code, i.e. no extra conditions, no “missing” conditions.
In later versions, it only shows up if there are missing conditions on New Code. Here’s an example from our dogfooding instance. This is the Java language analyzer. It’s assigned to the SonarSource way - JVM squad Quality Gate which has extra conditions, but no warning on the projects.
Versus SonarLint for Eclipse, which is assigned to a Quality Gate that omits coverage (in addition to having additional conditions).
HTH,
Ann