The issue was ignored on the branch (new Code = Compared to master) and didn’t occur on the master (new Code = Since Version change), which is strange, as the code was not changed in the branch.
We assume it might be because of the missing blame information mentioned in the log.
“Missing blame information” seem to be mentioned in the logs from time to time, but rarely. And they do not seem to always cause “new” issues.
So I have the following questions:
Could the new occurrence of the issue be caused by the missing blame information?
Why are the blame information missing at all? The CI-build always executes the same script, but the message only occurs sometimes. But when it occurs, the same files are affected, all in the same 2 packages.
The screenshot shows something related to architecture, which is recently introduced, so it’s of necessity a newly detected issue, altho I normally would have expected it to be backdated (there are some exceptions to that.)
Yes. If blame information was missing in the analysis where this issue was first detected, then backdating would have failed and it would be seen as new.
At a guess, you don’t have all the prerequisites fulfilled on all your build agents. These are listed in the context of PR analysis, where they’re crucial, but they also apply in general.
thanks for your explanation. We are using several build agents, so a misconfiguration on one of them might explain, why this problem doesn’t occur on each analysis.
I will have the build agents checked and get back to you.
The “Missing blame information” always referred to the same files, all located below the same folder. The last change on them was renaming the parent folder from mymapper to myMapper.
While this is a change for git (case-sensitive) it is not considered a different name by Windows (case-insensitive). Therefore this change was not reflected in the local git repository of the Windows build agents. So Sonar was asking for blame information for …\mymapper\example.java (the name from the local repo) which git couldn’t provide, as git only knows …\myMapper\example.java.
On some of the build agents, the repo was checked out after the renaming, leading to the correct folder name in the local repo. That’s why on some agents it worked, on others it didn’t.
We are going to correct the local repos, which will hopefully fix this problem.
