[Bug][Module Name] Sonar qube data is not consistent about incubator-devlake HOT 5 OPEN

Hi , did you conduct any scans during Aprile 19th and 29th?

from incubator-devlake.

Hi @naveenreddymanukonda , the current logic for SonarQube is that:

Before collecting SonarQube's data, DevLake will clear the existing data for SonarQube, and then start collecting the new data.

The purpose is not to mix the data of multiple Sonar scans up.

from incubator-devlake.

@Startrekzky Can you explain how this works? Does it replace existing data for past days or for the same day? Also, if DevLake clears data, why did we have old data for a month?

from incubator-devlake.

@naveenreddymanukonda

1. SonarQube's data is organized by scans.
2. SonarQube's APIs can only be used to get the data for the last scan.

So, DevLake's SonarQube plugin will always collect the full data from SonarQube, which is the result of the last scan. But before that, we'll remove the existing data in DevLake's DB, the data might be the result of the previous Sonar scan.

from incubator-devlake.

@Startrekzky Let's save this scan data to track how defects are resolved over time. If we run SonarQube 10 times a day, we can just keep the latest record for that day.

Idea is to show this data in a trend chart.

Happy to discuss and contribute on this requirement

from incubator-devlake.