[Bug][Module Name] Sonar qube data is not consistent

[naveenreddymanukonda]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

I'm noticing inconsistencies in the SonarQube data stored in cqissues. It seems like some data might be getting deleted after a week. I can't find information from a week ago, even though the screenshot shows values for April 29th and 19th. There's a gap in the data between those dates.

We are referring cqissues table

Where we did some pushes into Sonarqube.

What do you expect to happen

We need to have the data whenever we run the scan

How to reproduce

NA

Anything else

No response

Version

v1.0.0-beta6@ea2cdbc

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[Startrekzky]

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

[Startrekzky]

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.

[naveenreddymanukonda]

@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?

[Startrekzky]

@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.

[naveenreddymanukonda]

@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