Our team is facing pipeline timeout on Bitbucket Cloud due to very long SonarCloud analysis. Usually, the analysis time can be kept manageable thanks to the server cache. However, when running the analysis for a branch (whether it’s a short-lived or long-lived one), it seems no server cache is used at all. I’m seeing this in the logs:
Could you add -Dsonar.verbose=true to your analysis command and provide the full analysis log, redacted as necessary? It should help us see where the time is going.
Can you please try to open the file with a different application? The file is relatively big, maybe the viewer you’re using is struggling because of that.
I’m still not able to get a readable download of the file, but I asked a colleague to double-check the file for me. It’s readable for him (what’s your OS?) and he pointed out that this is a log for a short-lived branch. The cache only kicks in for PR analysis.
Thanks to you and your colleague.
I’m using Ubuntu 22.04.
Sorry to repeat myself, but I need clarifications.
If the cache “only kicks in for PR analysis”, why the documentation seems to state the opposite? Or maybe I’m misinterpreting it. Since it’s nowhere mentioned that cache isn’t used for branch analysis I’d strongly suggest updating the docs to point it out, if I may.
Unfortunately, as far as I know, not using the cache means for us that there’s no easy way to prevent our analysis from exceeding the allowed time.
Sorry, I forgot we were dealing with a CFamily language. That cache was developed first and works a bit differently than for the rest of the languages.