Currently, I’m using Sonar (SonarQube Version 6.7.5 build 38563) on a server.
I’ve encountered a problem related to the backdating when scanning an old project.
The old codes produced old issues that have the date of scan, not the date of commit.
This is the scan chronology until now:
- 26 Sept 2018, First scan. The dates were correct. Version was ‘not provided’
- 3 Oct 2018, The quality profile was changed. The dates were correct. Version was still ‘not provided’
- 10 Oct 2018, The quality profile was changed. Version was Baseline.
There are 2 new errors in the old codes.
- 17 Oct 2018. No quality profile changes. Version was 5.0.0.
The errors from 10 Oct 2018 were fixed by themselves.(Resolution = fixed, Status = closed). But there are 2 new errors.
- 24 Oct 2018. No quality profile changes. Version was still 5.0.0.
No new error.
- 31 Oct 2018. No quality profile changes. Version was still 5.0.0.
Somehow one of errors from 17 Oct 2018 was fixed.
- 7 Nov 2018. The quality profile was changed. Version was still 5.0.0.
There are 2 new errors.
- 14 Nov 2018. No quality profile changes. Version was still 5.0.0.
The errors from 7 Nov 2018 were fixed by themselves. But there is a new error again.
Important Note: There is no changes at all on the SCM and the project has over 7000 files.
So far, I have tried to re-scanned while replicating the quality profiles’ changes on my local version. It has similar problem with different bugs that has wrong backdating…
I would like to know whether this sonar’s bug or the side effect of changing the quality profile or because of the massive amount of files that may potentially create this problem or the external thing that may cause this problem?
Or if this is not a problem. Why the issues did appear even though there is no changes in quality profile and the code?
Thanks for your attention. Sorry for the long question.