Upgrade sonar-scanner binary in built-in Sonarqube Scan Step
in progress
L
Logical Chameleon
We are updating our Sonarqube Server installation to 2025.5.0 shortly and have been given a recommendation that clients interacting with that should use sonar-scanner version 7.1.0 to prevent incompatibility issues. We would like the builtin Sonarqube scan step/plugin to be updated to allow us to specify the updated sonar-scanner version, or use the newer version by default.
Log In
G
Gold Macaw
Hi Pritesh Chandaliya and Harness team,
I have a couple of questions regarding SonarQube compatibility.
SonarQube has released Sonar Server version 2026.1, which requires a minimum Sonar Scanner CLI version of 8.0.1.
Could you share whether there is a planned timeline for updating the Harness SonarQube step to support this requirement? Specifically, will the step be updated to remain compatible with SonarQube’s latest supported versions?
More broadly, is there a standard process or cadence for keeping the SonarQube integration aligned with upstream SonarQube releases and their scanner requirements? Since SonarQube is provided as an out-of-the-box feature, it would be helpful to understand how compatibility updates are managed without needing to raise support tickets or submit enhancement requests each time a new version is released.
Appreciate any clarity you can provide on roadmap and maintenance expectations.
Thank you
This post was marked as
in progress
Pritesh Chandaliya
marked this post as
under review