Must-share information (formatted with Markdown):
- which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
- Version 9.9 (build 65466)
- how is SonarQube deployed: zip, Docker, Helm
- on a VM
- what are you trying to achieve
- Leverage Bors (GitHub - bors-ng/bors-ng: 👁 A merge bot for GitHub Pull Requests) to merge development branches into feature branches or main.
- what have you tried so far to achieve this
- sometimes we have no issues, sometimes, it seems that the issue gets stuck in Sonar.
Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!
- sometimes we have no issues, sometimes, it seems that the issue gets stuck in Sonar.
We use bors to handle all merges into main
, our epic branches and our release branches. Bors does this by building a branch called staging
. We will occasionally have a situation where an issue will appear on staging, and it may be a while for the developer to get around to fixing it. This will correctly cause a build to fail.
Often times this is an old issue (like Similar tests should be grouped in a single Parameterized test
) to appear as new. Subsequent staging builds fail even though they have not introduced the issue.
Does anyone have a recommended workflow for this? Would deleting the branch in SQ help?