Only the latest version of SonarQube Community Build is considered active, so you’ll need to upgrade and see if the situation is still replicable before we can help you.
I upgraded to sonar 25.3, however same issue only the files in the sonar.inclusions are being scanned but the previous scan is being overridden and I cannot check the issues of the other files.
So to sum up, I scanned 3000 sql files and have for each file its issues.
I modified a file and want to re run the scanner to check if the issues are fixed.
However the other 2999 sql files are still untouched so there is no need to rescan them.
When I ran the scanner on the directory that contains these sql files in rescanned all of them.
I tried scanning another time but this time I specified in the sonar.inclusions what file to scan and it only scanned the file I want, but removed the analysis of the other files
In versions, you could use pull request analysis for this.
In Community Build you’re going to need to carefully craft your sonar.inclusions each time.
That said,
analyses are not additive. If you run an analysis of only the one or two changed files, then all the rest of the files will disappear from your project.