As you can see in the screenshots below, for reasons that are unclear to my team and I is that the total number of SonarQube issues sometimes changes between brief periods of time.
I’ve been looking around the web, but couldn’t find any similar questions around, but we’re suspecting that it might have something to do with running multiple (Angular front-end) builds in our Jenkins pipeline as opposed to a single one.
Is this a familiar problem to anyone?
You’re seeing Code Smell and Bug counts toggle back and forth at intervals. There are several possible causes of this. The easy ones are:
- Quality Profile changes (they would be noted in the list of analyses on the left and that’s not showing up in your screenshots, but for thoroughness…)
- Changes to what’s analyzed (can you check the graph of LOC to see if it fluctuates too?)
- exclusions settings
- changes to what’s checked out
It could also be worth looking at analysis logs if you still have them.
I’ll be honest & say that we see something like this about every 9-12 months & rarely is the cause reported back to us. I don’t know if it’s because people never figure it out or because they just don’t get around to letting us know.
Thanks for reaching out Ann,
I’m in the process of looking into the possible causes that you gave and so far I’ve been able to check that there were no Quality Profile changes during that exact time.
Languages being used:
HTML, CSS & Typescript
Screenshots take June 25th:
2nd Post because of restriction on posting screenshots.
The Lines of Code show no changes either during that time:
A colleague did observe that the difference in issues during the ‘bump’ that we experienced is extremely close to the number of our (registered to SonarQube) ESlint errors. Therefore there might be a possibility that our linter errors weren’t fed to SonarQube at the moment of the ‘bump’.
I might know more when I gain access to the location of the Analysis Logs, which is now only accessible to our DevOps engineers. I’m hoping that’ll be oncoming week.
Thanks for checking in.
This is intriguing. I look forward to hearing more. And I’ll try to remember this in future if we get similar reports.