Sonarqubes quality profile gate plugin integration issue with jenkins

Hi Team,

Thanks for the help.

As per the request : Sonarqube not working - Get help / SonarQube - SonarSource Community we upgraded the sonarqube to the latest LTS version( sonarqube-8.5.7).

But when we are running the sonarqube from the Jenkins, the build is getting scanned but the build is failing with the below failure :

org.quality.gates.jenkins.plugin.QGException: Expected status 200, got: 400. Response: {“errors”:[{“msg”:“The \u0027component\u0027 parameter is missing”}]}
at org.quality.gates.sonar.api.SonarHttpRequester.executeGetRequest(
at org.quality.gates.sonar.api.SonarHttpRequester.getAPITaskInfo(
at org.quality.gates.sonar.api.QualityGatesProvider.getAPIResultsForQualityGates(
at org.quality.gates.jenkins.plugin.BuildDecision.getStatus(
at org.quality.gates.jenkins.plugin.QGPublisher.perform(
at hudson.tasks.BuildStepMonitor$1.perform(
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(
at hudson.model.Build$BuildExecution.post2(
at hudson.model.AbstractBuild$
at hudson.model.Run.execute(
at hudson.model.ResourceController.execute(
Build step ‘Quality Gates Sonarqube Plugin’ marked build as failure

and we are using below quality gate profile in our Jenkins :

And below is the sonar profile in the Jenkins :

Though sonarqubes is running fine in our linux machine still the builds are failing at the quality gate profile stage.

Please advise further.

Thanks in advance.

Uploading: sonarqubes_profile.png…

Hi Team,

Please read the sonarqube instance mentioned above as sonarqube-8.9.7.
It is a typo.

Please help on the above request at the earliest convenience.

Thanks and Regards,

It seems to be a bug on the “Sonar Quality Gates Plugin”. This plugin doesn’t support SQ 8.x+ and the fix wasn’t merged by the maintainers yet: Added support for SonarQube 8.0-8.8 by kcbaltz · Pull Request #17 · jenkinsci/sonar-quality-gates-plugin · GitHub

As an alternative, you could disable this plugin and add the parameter sonar.qualitygate.wait=true to the analysis step, as described on Overview | SonarQube Docs

Setting sonar.qualitygate.wait to true forces the analysis step to poll your SonarQube instance until the Quality Gate status is available. This increases the pipeline duration and causes the analysis step to fail any time the Quality Gate fails, even if the actual analysis is successful. You should only use this parameter if it’s necessary.

Hi Team,

Just an update…!!

We can bypass the Quality Gate Profile portion but the question arises how can we scan the code because in the Quality Gate Profile, we basically define the rules which will be scanned accordingly and the results can be scanned.

Could you please suggest any other alternative plugin which we can integrate with our jenkins and if so, at what stage to imitate the action of Quality Gate Profile.

Or if no such plugin is available, then how do we fix this plugin issue as it’s not producing the desired scanning reports in the sonarqubes ui page.

Please help on this asap.

Thanks in advance.