We’ve migrated our SonarQube instance from 6.7.1 Community Edition to 7.7 Developer Edition.
We launch the scans of (small) projects from Jenkins and the background tasks are correctly scheduled. However, they never finish and the progress is not visible in the logs:
First, sorry for the delay in responding. I’m glad it’s working for you now(?).
I’m not saying nothing’s wrong on the SonarQube side but your experience doesn’t ring any bells for me. I would actually first look at whether the experience is reproducible, and if it’s not or it’s only reproducible intermittently I’d look at what else is going on in the environment (resource constrains in network, db, …)
I know this isn’t very helpful. I’m happy to help go further if we can identify something more concrete.
The issue has not come back, but for the fact that sometimes, the background task takes more time to complete than in average.
We use a lot of monitoring for the tools in our CI/CD ecosystem. Is there a way to make SonarQube export stats about background tasks processing in Prometheus for example?
please take a look at the api api/ce/activity, which return the background tasks queued in the compute engine. You can filter by type=REPORT and status=SUCCESS and look for the executionTimeMs.