Dear SonarSource team,
First of all, congrats on the amazing improvement in Java analysis you managed to implement in SonarQube 9.4!
Now we are using SonarQube Dev Edition 9.5 and it would be great to get a list of the rules that are executed for the untouched Java files in a PR
Before the introduction in 9.4 of the feature to not execute all rules for all classes, my Java analysis used to take almost an hour. Hence, the team decided to implement a mechanism to pass only the touched class as sonar.inclusions, even if we knew that this could result in an issue found only when the PR is merged in the main branch as we weren’t analyzing the unmodified files at all.
However, now that you’ve done something similar (but better!), we’d like to remove our custom workaround and just leave the built-in feature. When testing it, we observed that analyses for PRs take 4-5 min more than the one we implemented, but we were not able to reproduce any scenario in which the analysis failed due to an issue in a non-modified file. Due to this, the team would like to make sure that this change would benefit us to compensate for the increase in execution time.
Therefore, we’d love to have a list of these special rules to come up with a case ourselves, or (even better), get just some basic examples of how to reproduce a bug in a non-modified file.
Looking forward to reading from you!