CI build runs Sonar task successful but it says last analysis has failed

SonarQube Cloud
1

  • ALM used: GitHub

  • CI system used: GitHub actions

  • Scanner command used when applicable (private details masked):

    SonarSource/sonarqube-scan-action@v7

    with:

    projectBaseDir: .

    scannerVersion: 8.0.1.6346

    scannerBinariesUrl: https://binaries.sonarsource.com/Distribution/sonar-scanner-cli

  • Languages of the repository: TypeScript

  • Only if the SonarCloud project is public, the URL

    • And if you need help with pull request decoration, then the URL to the PR too

  • Error observed: 16:35:02.393 INFO ANALYSIS SUCCESSFUL, you can find the results at: https://sonarcloud.io/dashboard?id=foobar

    16:35:02.393 INFO Note that you will be able to access the updated dashboard once the server has processed the submitted analysis report

    16:35:02.393 INFO More about the report processing at https://sonarcloud.io/api/ce/task?id=AZwpgdvijbB1sw11F-ov
    But on SonarCloud in the project it says “last analysis failed“ and “number of lines exceeded“. I have checked and we are below the quota limit.

2

Hi,

You’re not over your line limit yet. Your CI successfully submitted an analysis report to SonarQube Cloud. That’s the ‘analysis successful’ part. The message on the server is telling you that if that particular analysis were processed, you would be. So to keep from basically locking you out, the analysis report is discarded rather than being processed.

At a guess, something in the relevant project changed to

  • add libraries
  • add generated files
  • update configuration to analyze previously ignored files

so that suddenly analysis is finding a lot more lines than it should.

Unfortunately there aren’t a lot of tools to help you figure this out except to set sonar.verbose=true in your analysis parameters and check your analysis log for the files being indexed.

 
HTH,
Ann

3

Ann, thank you for your kind response. I think in our case, the reason was that I deleted the project in sonarcloud, and then re-created it and ran the analysis on our “main“ branch. But the pull request analysis failed because the PR branch was branched off from an older commit of the main branch. After rebasing the PR branch onto the top of the main branch (the analyzed commit), everything worked again.

1 Like
8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.