- ALM used- Azure DevOps
- CI system used Azure DevOps
- Language - dotnet/C#
I am migrating from v2 Sonarcloud Azure Devops tasks to v3.
I was following the guidance after receiving this warning
##[warning]Task 'Prepare Analysis Configuration' version 2 (SonarCloudPrepare@2) is deprecated.
##[warning]This task is deprecated. Please upgrade to the latest version. For more information, refer to https://docs.sonarsource.com/sonarcloud/advanced-setup/ci-based-analysis/sonarcloud-extension-for-azure-devops/
SonarCloudAnalyze@3 now outputs all the findings as warnings into the pipeline.
Is there a way to change this behaviour? My initial expectation was to decrease the warnings in the pipeline, not increase them. The old task is less noisy.
Our workflow involves IDE/linters, having 0 warnings on build time, internal standards compliance check and Sonar as the last resort to validate the rest of our code, so the alerts don’t normally reach “bug” or “blocker” levels. If they do, we review the results on the SonarCloud SaaS page.
I find these warnings to be noise.It is impossible to distinguish between “useful” alert and a “recommendation” on the interface and it does more harm than good.