Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-60049

Sonar Quality Gate plugin Throwing 400 after 8.0 Upgrade

    Details

    • Similar Issues:

      Description

      After SQ upgrade the plugin throwing an error 

      "msg":"The 'component' parameter is missing"}]}"msg":"The 'component' parameter is missing"}]} at org.quality.gates.sonar.api.SonarHttpRequester.executeGetRequest(SonarHttpRequester.java:124)

      The Jenkins Plugin used : 1.3.1 

      The SQ community passed a reference https://community.sonarsource.com/t/the-component-parameter-is-missing/13736/4  

        Attachments

          Activity

          Hide
          adig Adi Godkin added a comment -

          This seems like a compatible issue with the "components" api - the parameter is no longer ProjectKey, instead should be replaced with "component" (parameter) - 

          /api/components/show?component=%s

          Show
          adig Adi Godkin added a comment - This seems like a compatible issue with the "components" api - the parameter is no longer ProjectKey, instead should be replaced with "component" (parameter) -  /api/components/show?component=%s
          Hide
          wissemwis wissem Hamza added a comment -

          Hi,

          After upgrade, the plugin is using 'org.quality.gates.sonar.api60.SonarHttpRequester60' class to communicate with sonarqube api instead of 'org.quality.gates.sonar.api61.SonarHttpRequester61' class.

          Is there someone who can fix this bug ?

          Thanks.

          Show
          wissemwis wissem Hamza added a comment - Hi, After upgrade, the plugin is using 'org.quality.gates.sonar.api60.SonarHttpRequester60' class to communicate with sonarqube api instead of 'org.quality.gates.sonar.api61.SonarHttpRequester61' class. Is there someone who can fix this bug ? Thanks.
          Hide
          pirxdanford Pirx Danford added a comment -

          I am facing the same error, oddly enough exactly the same plugin version is working fine on another Jenkins instance. Any help in resolving this is appreciated.

          Show
          pirxdanford Pirx Danford added a comment - I am facing the same error, oddly enough exactly the same plugin version is working fine on another Jenkins instance. Any help in resolving this is appreciated.

            People

            • Assignee:
              ivanash Ivana Sh
              Reporter:
              jvishnu vishnu jam
            • Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: