Does SonarSube really understand the impact of his on their clients using Azure DevOps ?(?).
We are force to reconfigure 70 (!) projects. I read that we are lucky as there are client that need to take actions on 500 projects.
I already planned some time next week for these 70 projects but now I got the feedback that a lot of decisions that were made previously have to be re-takane again.
For us we are talking about noise generated on our pull request that represent 75K (!N) thousands issue.
Why this decisision was taken is unclear to me but I think it was an optimisation on SonarQube side to make their lives easier.
Sorry, excuse me.
This is adressed by an update to the release notes. Are we an edge case? I don’t understand what you are doing SonarQube.
This is a repost from SonarQube 10.0 not reporting quality gate status and PR decoration in Azure DevOps - #17 by Tom_Pester
I normally don’t repost to be clear.