We currently use sonarcloud in our CI/CD pipeline to perform an analysis on new code and pull requests. Lately we have seen some degradation in the performance of sonarcloud.
In our Jenkins pipeline a sonarscanner command is fired which should trigger an analysis on sonarcloud. Up until last week it went fine, but we noticed that the Jenkins step is waiting on response from sonarcloud to mark the analysis as complete. When we look in the background tasks, we actually see that the analysis is triggered, but has the pending status. Sometimes it will hang at this point and our Jenkins build will fail because of the timeout. There is no way to trigger the analysis from pending to started, even with the restart trigger. This behaviour also sometimes happens with pull requests, where a completed sonar analysis is a mandatory check. When this happens we are not able to merge, because we don’t get any response back from sonarcloud.
Our current workaround is to completely disable the sonar analysis altogether, but this is not something which is a working solution for us in the long run. We would like to know why the performance of sonarcloud went down the last few weeks.