22.214.171.124563 (LTS) and attempting to utilize the Quality Gates to flag issues on new code, and not force teams to immediately go back to fix older issues (Old codebase, lots of issues).
Running SonarQube analysis from TFS build.
What I see happen, I create a new project in Sonar from a baseline build of our Develop branch… later a branch is taken from develop, and is built… it will succeed and pass the quality gate… later a change to that same branch will happen, and the quality gate will FAIL with dozens of issues, with code that hasn’t changed in months or years… I thought that the quaility gate against the leak period would allow us to ignore OLD issues and focus on NEW issues, but that doesn’t seem to be happening, and I don’t understand how those old issues seem to be getting flagged as new issues…
The documentation on the Quality gate itself says:
If focuses on keeping new code clean, rather than spending a lot of effort remediating old code. Out of the box, it’s already set as the default profile.