In our DevOps pipeline sonar scan is completing within 10mins including solution building. But in sonar server it is taking 24 mins additional time to upload the updated scan results in project. We are using community edition version of sonarcube 10.6version and know parallel processing is not possible which is seperate topic. but in devops pipeline already scanned project why it is taking 24mins again to upload the report. I’m attaching here the snapshots and pipeline logs for more details. Please help as we need to reduce the scan completion time.
According to your log (thanks for leading with that!) the upload happens in 3452ms, or 3.452 seconds. I suppose the complaint is that it takes 24 minutes to process the uploaded report, server-side? For that, you should
Make sure your SonarQube server, and particularly the CE (compute engine) process has plenty of resources. That’s tuned with the sonar.ce.* properties.
Make sure your SonarQube server is close to the DB on the network. Processing the analysis report and storing the results is very DB-intensive.
Beyond that… based on your analysis log, this is a really, really big project. I’m not sure there’s much else you can do. Even the parallel processing available in Enterprise Edition($$) wouldn’t help here because according to your screenshot, this wasn’t 24 minutes waiting in the queue, but 24 minutes processing the report.
