I’m running Community v9.6 and we have scans for a project for the ‘dev’ branch continuously, but also for a ‘release’ branch (created from dev branch, only during the end of a quarter).
Developers can close some of the open issues (as Won’t fix ) in dev branch including a comment. But then once ‘release’ branch is scanned at the end of the quarter, then those (already closed in dev) issues will be detected again. So developers will need to review those again for the release branch.
Is there a way to close those issues as well in ‘release’? We were thinking about using the API, but not sure if t allows to identify that closed issues for an specific period of time.
Unfortunately, issues are synched across branches at branch creation and not subsequently.
This is something that’s been on our radar for a while, but never floated to the top (to mix a metaphor) of the list. I’ll make sure the Product Manager is aware of your need.
Make sure you upgrade to SonarQube v9.9 LTS soon, not only to benefit from our Best LTS Ever™, but because soon we will systematically ask users to upgrade when they ask questions about earlier versions of SonarQube, which are now considered unsupported.
How do you merge the code from the ‘dev’ branch to the ‘release’ branch? If you are using a PR for that, I would expect the issues to be also automatically closed as Won’t fix in your ‘release’ branch when the branch is reanalyzed.
Thanks for your answer.
I’m really interested on what you mention about that issues are synched at branch creation. In the case that I explained before, if I remove and scan again the release branch, will the already closed issues in dev branch be closed as well after that recreation?
BTW we have planned for the update, we are just waiting for some releases to happen in order to avoid new rules to impact on products at that point
In the first analysis, issues are synched from your
main branch, so assuming dev is your
main branch, then yes.
Thank you so much Ann for your answer.