we are having troubles that SonarQube shows old issues for short living branches, however the behavior is somewhat random. It looks like the old code is more likely to show up if it’s being changed in some other branch of our project. We use git rebase strategy for branching.
What is also suspicious (and maybe connected to this problem) is that in the UI we don’t see GIT commits and commiter names, just dates:
also it doesn’t show any highlight for new code and this is the only date mark in the whole file, even it’s been composed by many commits in the history.
I searched the forums, but didn’t find any similar issue, so probably there is some obvious settings to be used.
Any help will be really appreciated.
Must-share information (formatted with Markdown):
- which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
SonarQube 7.7 developer edition, sonar-scanner-18.104.22.1687-linux
- what are you trying to achieve
clean new code analysis
- what have you tried so far to achieve this
normally the tool is supposed to work like that in default configuration