- ALM used: Azure DevOps
- CI system used: Azure DevOps
- Scanner command used when applicable (private details masked)
- Languages of the repository: C#
In our environment we have several Visual Studio solutions in a single Azure DevOps Git Repo. (This was done for management purposes.) Each build represents a Visual Studio solution within the repo. Each build is associated to a SonarCloud project.
When a Pull Request is created, Azure DevOps (through the branch policies) is able to kick off multiple builds; which results in multiple SonarCloud analysis runs.
When the first build is analyzed, the PR receives the comments from SonarCloud. When the second (or any later) build is analyzed, the previous analysis comments from SonarCloud on the PR are deleted. This makes it hard to track the comments from multiple builds.
Instead of deleting the PR comments, could there be an option to leave the comments available and mark them “Closed” or “Resolved”?
I understand the best approach would be to refactor our code base so that each Visual Studio solution is in it’s own Git repo, but the team has pushed back on this for various reasons.