- Which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)?
- Community Edition Version 9.0.1 (build 46107)
- How is SonarQube deployed: zip, Docker, Helm?
- Helm
- What are you trying to achieve?
- Whenever a dev makes an MR, the SonarQube bot triggers a scan. After subsequent commits to that same MR, the bot will add a new comment with any new scan results. If any issues are fixed by the dev, it will “resolve” its own threads, but if more issues come up it will create a new thread. Supposedly it should be editing its originally scan comment, not making new ones. Instead, this happens:
(this is after the dev made two commits: the bot makes two comments)
- Whenever a dev makes an MR, the SonarQube bot triggers a scan. After subsequent commits to that same MR, the bot will add a new comment with any new scan results. If any issues are fixed by the dev, it will “resolve” its own threads, but if more issues come up it will create a new thread. Supposedly it should be editing its originally scan comment, not making new ones. Instead, this happens:
- What have you tried so far to achieve this?
- I’ve been reading through other community posts and the docs but as far as I can tell, the default MR behavior is to edit the original comment. That’s not happening for us though, and I can’t find any configuration for this behavior.
Whoops, disregard! I just learned that we actually use GitHub - mc1arke/sonarqube-community-branch-plugin: A plugin that allows branch analysis and pull request decoration in the Community version of Sonarqube, so I’ll ask there. 
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.