Massive slowdown of scans using GitHub Actions

SonarQube Cloud
, , ,
1

We have noticed a massive slowdown in the scans for our code base using GitHub Actions. The project is mostly JavaScript and has ~6k files and ~190k lines of code. Typically the scan would take about 30 minutes, but it’s now timing out after 6 hours (the max for a GitHub Action).
We’ve seen this with both sonarsource/sonarcloud-github-action@cb201f3b2d7a38231a8c042dfea4539c8bea180b and sonarsource/sonarcloud-github-action@5875562561d22a34be0c657405578705a169af6c. We are using GitHub’s ubuntu-22.04 runner.
What can we do to get the process time back down to normal?

2 Likes
2

Hi @dancook-sl,

Please see THIS announcement thread regarding the issue.

Best,
Tobias

1 Like
3

Thanks for sharing that link. This looks like an issue I would have expected to see on the SonarCloud Status page https://sonarcloud.statuspage.io/history. In the future, how can I know when an ongoing incident impacts my use of the service?

4

Also, I am still seeing a slowdown in the scanning process. Is there any further word on resolving these issues?

7

Hi @dancook-sl

Could you activate the debug mode (by adding an argument to the action -Dsonar.verbose=true), and post here the full execution log with timestamps, for us to investigate where the slowness comes from?

Thanks in advance,
Claire

8

This eventually resolved itself, and the runs are back to more normal times of <10 minutes.

9

I’m glad to hear that, and I hope it will stay like this!

Have a nice day,
Claire

11

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.