We get allot of warnings from auto-generated code which we want to hide in the Azure pipelines. It’s cluttering and hiding real warnings that may occur in the pipeline.
It could be either a checkbox in the SonarCloudPrepare@x task to show/hide these warnings, or use the sonar.exclusions input.
Hear, hear! Anything that can be configured as input, such as exclusions or how certain warnings are handled, should also be applied consistently in earlier stages. Otherwise, the pipelines and the SonarCloud UI end up showing different representations, which is not preferable.