SonarQube dashboard master branch not updated after analysis success via Sonar scanner on Jenkins

I, I am pretty new to configuring Sonar Qube on a git repository. I am running the sonar scanner in the Jenkinsfile of my project. It works really well regarding my Pull Requests. I am able to see the results of the analysis in SonarQube as expected on the SonarQube Dashboard (web browser).

But for my master branch (main branch), I am unable to see the most recent analysis performed by Jenkins. I can see in the logs of Jenkins that the analysis Succeeded and was uploaded to SonarQube. But in Sonar Qube iself, it only shows the analysis from 2 years ago.

Here are the logs of the success (Jenkins logs) :

16:28:35.798 INFO: ANALYSIS SUCCESSFUL, you can find the results at: (I HID the link on purpose)

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

16:28:35.798 INFO: More about the report processing at (I HID the link because of confidential information)

16:28:35.801 DEBUG: Post-jobs : 

16:28:35.820 INFO: Analysis total time: 33.658 s

16:28:35.821 INFO: ------------------------------------------------------------------------


16:28:35.821 INFO: ------------------------------------------------------------------------

16:28:35.821 INFO: Total time: 43.533s

16:28:35.944 INFO: Final Memory: 61M/214M

16:28:35.944 INFO: ------------------------------------------------------------------------

I can see in the link about the “report processing” that it is taking the information of the failed analysis from 2 years ago… And not from the actual most recent code…

"errorMessage":"This analysis will make your organization (Hidden Organization name) to reach the maximum allowed lines limit (having 507811 lines).

Here is the Overview on SonarQube :

And an view of the “master” branch :

Here is the Jenkinsfile code regarding the Sonar Qube analysis :

                    when{ changeRequest()}
                                sh ' /home/jenkins/.sonar/sonar-scanner-' +
                                        ' -Dsonar.pullrequest.key=${CHANGE_ID}' +
                                        ' -Dsonar.pullrequest.branch=${BRANCH_NAME}' +
                                        ' -Dsonar.pullrequest.base=${CHANGE_TARGET}'
                            branch 'master'
                            not { changeRequest() }
                            sh '/home/jenkins/.sonar/sonar-scanner-'

The same Jenkinsfile code worked well on another project that was started from scratch. Is it possible that it fails to update the Sonar Qube dashboard because of the previous analysis failure from 2 years ago? If so, is there a way to delete said analysis or branch completely from Sonar Qube to start anew?


Welcome to the community!

It’s not quite clear to me where you see this message, but this error would definitely prevent your analysis report from being processed. Did you add a lot of code to the project in the last 2 weeks? Or add analysis of new projects?


This message appears in the logs of jenkins in the form of an url. I have confirmed with my organization, it seems that we are paying for 500 000 lines. With my new project added we are now at 507 811 lines of code being analyzed among the organization.

I just wasn’t sure if the issue was regarding my configuration of the project or my organization, that’s why, in the meantime I asked on the forum for help!

I will wait to see what happens once we change our plan! I will close this ticket as soon as it works.

1 Like