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

waitForQualityGate getting a wrong analysisID

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • sonar-plugin
    • None

      Using withSonarQubeEnv in dockerfile agent, successive waitForQualityGate abortPipeline true results in a wrong analysisId, AXyLfj5JlX0w7MRERt_e in my case, that seems a default one, raising a Not Found on Sonarcube server. (api/qualitygates/project_status?analysisId=AXyLfj5JlX0w7MRERt_e).

      Edits:
      Checking status of SonarQube task 'AXyLfjqvdOUyxmZtXP4E' on server 'Sonarqube'
      SonarQube task 'AXyLfjqvdOUyxmZtXP4E' status is 'SUCCESS'

      It's checking totally another task that I don't know where come from. Seems an old generater ID and sticked with that forever.

      Full error in case:
      org.sonarqube.ws.client.HttpException: Error 404 on http://XXXX:9000/api/qualitygates/project_status?analysisId=AXyLfj5JlX0w7MRERt_e : {"errors":[

      {"msg":"Analysis with id \u0027AXyLfj5JlX0w7MRERt_e\u0027 is not found"}

      ]}

          [JENKINS-66912] waitForQualityGate getting a wrong analysisID

          Ixiodor Ixiodor created issue -
          Ixiodor Ixiodor made changes -
          Description Original: Using withSonarQubeEnv in dockerfile agent, successive waitForQualityGate abortPipeline true
          results in a wrong analysisId, AXyLfj5JlX0w7MRERt_e in my case, that seems a default one.           		New: Using withSonarQubeEnv in dockerfile agent, successive waitForQualityGate abortPipeline true
          results in a wrong analysisId, AXyLfj5JlX0w7MRERt_e in my case, that seems a default one, raising a Not Found on Sonarcube server.
          Ixiodor Ixiodor made changes -
          Description Original: Using withSonarQubeEnv in dockerfile agent, successive waitForQualityGate abortPipeline true
          results in a wrong analysisId, AXyLfj5JlX0w7MRERt_e in my case, that seems a default one, raising a Not Found on Sonarcube server.           		New: Using *withSonarQubeEnv* in dockerfile agent, successive *waitForQualityGate abortPipeline true* results in a wrong analysisId, *AXyLfj5JlX0w7MRERt_e* in my case, that seems a default one, raising a Not Found on Sonarcube server.
          Ixiodor Ixiodor made changes -
          Description Original: Using *withSonarQubeEnv* in dockerfile agent, successive *waitForQualityGate abortPipeline true* results in a wrong analysisId, *AXyLfj5JlX0w7MRERt_e* in my case, that seems a default one, raising a Not Found on Sonarcube server. New: Using *withSonarQubeEnv* in dockerfile agent, successive *waitForQualityGate abortPipeline true* results in a wrong analysisId, *AXyLfj5JlX0w7MRERt_e* in my case, that seems a default one, raising a Not Found on Sonarcube server. (*api/qualitygates/project_status?analysisId=AXyLfj5JlX0w7MRERt_e*)
          Ixiodor Ixiodor made changes -
          Description Original: Using *withSonarQubeEnv* in dockerfile agent, successive *waitForQualityGate abortPipeline true* results in a wrong analysisId, *AXyLfj5JlX0w7MRERt_e* in my case, that seems a default one, raising a Not Found on Sonarcube server. (*api/qualitygates/project_status?analysisId=AXyLfj5JlX0w7MRERt_e*) New: Using *withSonarQubeEnv* in dockerfile agent, successive *waitForQualityGate abortPipeline true* results in a wrong analysisId, *AXyLfj5JlX0w7MRERt_e* in my case, that seems a default one, raising a Not Found on Sonarcube server. (*api/qualitygates/project_status?analysisId=AXyLfj5JlX0w7MRERt_e*).

          Edits:
          Checking status of SonarQube task 'AXyLfjqvdOUyxmZtXP4E' on server 'Sonarqube'
          SonarQube task 'AXyLfjqvdOUyxmZtXP4E' status is 'SUCCESS'

          He is checking totally another task that I don't know where come from.
          Ixiodor Ixiodor made changes -
          Description Original: Using *withSonarQubeEnv* in dockerfile agent, successive *waitForQualityGate abortPipeline true* results in a wrong analysisId, *AXyLfj5JlX0w7MRERt_e* in my case, that seems a default one, raising a Not Found on Sonarcube server. (*api/qualitygates/project_status?analysisId=AXyLfj5JlX0w7MRERt_e*).

          Edits:
          Checking status of SonarQube task 'AXyLfjqvdOUyxmZtXP4E' on server 'Sonarqube'
          SonarQube task 'AXyLfjqvdOUyxmZtXP4E' status is 'SUCCESS'

          He is checking totally another task that I don't know where come from.           		New: Using *withSonarQubeEnv* in dockerfile agent, successive *waitForQualityGate abortPipeline true* results in a wrong analysisId, *AXyLfj5JlX0w7MRERt_e* in my case, that seems a default one, raising a Not Found on Sonarcube server. (*api/qualitygates/project_status?analysisId=AXyLfj5JlX0w7MRERt_e*).

          Edits:
          Checking status of SonarQube task 'AXyLfjqvdOUyxmZtXP4E' on server 'Sonarqube'
          SonarQube task 'AXyLfjqvdOUyxmZtXP4E' status is 'SUCCESS'

          He is checking totally another task that I don't know where come from. Seems an old generater ID and sticked with that forever.
          Ixiodor Ixiodor made changes -
          Description Original: Using *withSonarQubeEnv* in dockerfile agent, successive *waitForQualityGate abortPipeline true* results in a wrong analysisId, *AXyLfj5JlX0w7MRERt_e* in my case, that seems a default one, raising a Not Found on Sonarcube server. (*api/qualitygates/project_status?analysisId=AXyLfj5JlX0w7MRERt_e*).

          Edits:
          Checking status of SonarQube task 'AXyLfjqvdOUyxmZtXP4E' on server 'Sonarqube'
          SonarQube task 'AXyLfjqvdOUyxmZtXP4E' status is 'SUCCESS'

          He is checking totally another task that I don't know where come from. Seems an old generater ID and sticked with that forever.           		New: Using *withSonarQubeEnv* in dockerfile agent, successive *waitForQualityGate abortPipeline true* results in a wrong analysisId, *AXyLfj5JlX0w7MRERt_e* in my case, that seems a default one, raising a Not Found on Sonarcube server. (*api/qualitygates/project_status?analysisId=AXyLfj5JlX0w7MRERt_e*).

          *Edits*:
          Checking status of SonarQube task 'AXyLfjqvdOUyxmZtXP4E' on server 'Sonarqube'
          SonarQube task 'AXyLfjqvdOUyxmZtXP4E' status is 'SUCCESS'

          It's checking totally another task that I don't know where come from. Seems an old generater ID and sticked with that forever.
          Ixiodor Ixiodor made changes -
          Description Original: Using *withSonarQubeEnv* in dockerfile agent, successive *waitForQualityGate abortPipeline true* results in a wrong analysisId, *AXyLfj5JlX0w7MRERt_e* in my case, that seems a default one, raising a Not Found on Sonarcube server. (*api/qualitygates/project_status?analysisId=AXyLfj5JlX0w7MRERt_e*).

          *Edits*:
          Checking status of SonarQube task 'AXyLfjqvdOUyxmZtXP4E' on server 'Sonarqube'
          SonarQube task 'AXyLfjqvdOUyxmZtXP4E' status is 'SUCCESS'

          It's checking totally another task that I don't know where come from. Seems an old generater ID and sticked with that forever.           		New: Using *withSonarQubeEnv* in dockerfile agent, successive *waitForQualityGate abortPipeline true* results in a wrong analysisId, *AXyLfj5JlX0w7MRERt_e* in my case, that seems a default one, raising a Not Found on Sonarcube server. (*api/qualitygates/project_status?analysisId=AXyLfj5JlX0w7MRERt_e*).

          *Edits*:
          Checking status of SonarQube task 'AXyLfjqvdOUyxmZtXP4E' on server 'Sonarqube'
          SonarQube task 'AXyLfjqvdOUyxmZtXP4E' status is 'SUCCESS'

          It's checking totally another task that I don't know where come from. Seems an old generater ID and sticked with that forever.

          Full error in case:
          org.sonarqube.ws.client.HttpException: Error 404 on http://XXXX:9000/api/qualitygates/project_status?analysisId=AXyLfj5JlX0w7MRERt_e : {"errors":[{"msg":"Analysis with id \u0027AXyLfj5JlX0w7MRERt_e\u0027 is not found"}]}
          Ixiodor Ixiodor made changes -
          Description Original: Using *withSonarQubeEnv* in dockerfile agent, successive *waitForQualityGate abortPipeline true* results in a wrong analysisId, *AXyLfj5JlX0w7MRERt_e* in my case, that seems a default one, raising a Not Found on Sonarcube server. (*api/qualitygates/project_status?analysisId=AXyLfj5JlX0w7MRERt_e*).

          *Edits*:
          Checking status of SonarQube task 'AXyLfjqvdOUyxmZtXP4E' on server 'Sonarqube'
          SonarQube task 'AXyLfjqvdOUyxmZtXP4E' status is 'SUCCESS'

          It's checking totally another task that I don't know where come from. Seems an old generater ID and sticked with that forever.

          Full error in case:
          org.sonarqube.ws.client.HttpException: Error 404 on http://XXXX:9000/api/qualitygates/project_status?analysisId=AXyLfj5JlX0w7MRERt_e : {"errors":[{"msg":"Analysis with id \u0027AXyLfj5JlX0w7MRERt_e\u0027 is not found"}]}           		New: Using *withSonarQubeEnv* in dockerfile agent, successive *waitForQualityGate abortPipeline true* results in a wrong analysisId, *AXyLfj5JlX0w7MRERt_e* in my case, that seems a default one, raising a Not Found on Sonarcube server. (*api/qualitygates/project_status?analysisId=AXyLfj5JlX0w7MRERt_e*).

          *Edits*:
          Checking status of SonarQube task 'AXyLfjqvdOUyxmZtXP4E' on server 'Sonarqube'
          SonarQube task 'AXyLfjqvdOUyxmZtXP4E' status is 'SUCCESS'

          It's checking totally another task that I don't know where come from. Seems an old generater ID and sticked with that forever.

          *Full error in case*:
          org.sonarqube.ws.client.HttpException: Error 404 on http://XXXX:9000/api/qualitygates/project_status?analysisId=AXyLfj5JlX0w7MRERt_e : {"errors":[{"msg":"Analysis with id \u0027AXyLfj5JlX0w7MRERt_e\u0027 is not found"}]}
          Kirk made changes -
          Component/s New: sonar-plugin [ 15523 ]
          Component/s Original: sonar-quality-gates-plugin [ 22523 ]

            arkanjoms Rafael Ramos
            ixiodor Ixiodor Ixiodor
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: