Must-share information (formatted with Markdown):
-
which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
We are using SonarQube Enterprise Version 9.9.0.65466 with the SonarScanner integrated into our CI pipelines. -
how is SonarQube deployed: zip, Docker, Helm
-
what are you trying to achieve
We aim to reduce the excessive Git clone operations performed during SonarQube scans. In one test case, we observed that a single SonarQube scan triggered 19 git clone operations, even though the PR involved minimal changes (only an update to the runner instance type). We are concerned that more substantial PRs could result in significantly higher clone operations, creating performance bottlenecks. -
what have you tried so far to achieve this
We have temporarily disabled the SonarQube scan job and removed it as a required check for pull requests to mitigate the strain caused by excessive Git clone operations on GitHub. However, we are now seeking guidance on configuration optimizations to reduce these clone operations while maintaining SonarQube scans in our pipeline.
Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!