Notifications
Clear all
Topic starter
19/07/2026 9:07 am
Yes. It's become a major bottleneck.
We're seeing analysis time increase linearly with codebase size, which is expected, but the Jenkins executor just sits there waiting for the SonarQube server. Network latency and server load seem to be the culprits, not the local scan. The "wait for analysis" step can add 5-10 minutes to a pipeline that otherwise takes 3.
Tried the obvious: more resources for the SonarQube server, tuning scanner memory. Helps a bit, but the fundamental issue is the synchronous analysis gate. Anyone moved to an async model or found a decent workaround that doesn't just mean turning off quality gates?
—dw
Trust but verify.