SonarQube cloud not recognize pull request

SonarQube Cloud
,
1

Template for a good new topic, formatted with Markdown:

  • ALM used GitHub

  • CI system used - Github actions

  • Languages of the repository- Node.js

SonarQube Setup

The SonarCloud GitHub app is set up on our organization, and automatic analysis is enabled. We’ve had multiple repositories using it successfully for a long time. However, we’re now encountering an intermittent issue that affects multiple repositories—it doesn’t seem to be isolated to any specific repo or project.

We’ve had multiple instances this week and last week where a Pull Request was opened and the analysis never showed up on the Pull Request. Also when we we went in to the “Pull Requests” section of SonarQube Cloud we could see the PR listed but it was showing up a blank page.

As a test, we recreated the changes on a new branch and that one did show up (same user, same code changes) sometimes but on some instances that also failed.

We also tried a few empty pushes to the PR because we hoped that maybe a webhook was missed by SonarQube Cloud from Github, but that also didn’t cause the PR to show up.

Because we have SonarQube as a required status check, this blocks the pull request and since additional pushes to the branch aren’t causing it to recognize the PR we have to create a completely new branch or disable this required check.

Any help on this would be greatly appreciated!

2

Hi team, just following up on this, we’d really appreciate it if you could take a look when possible. Thanks in advance!

3

Hi,

Do you see errors in the project? In Administration → Background Tasks?

Can you provide org and project Ids, as well as an approximate failure date/timestamp?

 
Thx,
Ann

4

Hello Ann,

Thanks for looking into this. No we don’t see any error in Background tasks.

In sonarcloud, under PR it shows like:
Last analysis failed Analysis ID “AZgXjmXxw1-FTpa7RY0t”

Your analysis with ID “AZgXjmXxw1-FTpa7RY0t” has failed because it took too much time. Please try another CI tool to analyze your project.

See troubleshooting documentation

Org: digitalRoute
Project Ids: dazzler-api , dazzler-engine

Currently experiencing issues with dazzler-api, with failures starting around 15th July at 14:30 and continuing until now. As a workaround we are bypassing the check as it is blocking the release process.

5

Hi,

So it sounds like you’re using automatic analysis, and that error is telling you your project has grown beyond where automatic analysis is appropriate. You’ll need to set up analysis in a CI. The docs should help.

 
Ann

6

Hi,

As I mentioned earlier, we have multiple projects under the digitalroute organization, and not all of them are experiencing this issue. Initially, it started with dazzler-engine, and now we’re seeing it with eye-dazzler as well.

I’m trying to understand why this limitation is affecting only certain projects — has the size or configuration threshold changed recently? And what exactly causes a project to “grow beyond” the limits of automatic analysis?

Appreciate any clarification on this.

Thanks!

7

Hi,

The error indicates that the project is too large or too complicated for automatic analysis. You’ve indicated that was not the case in the past. Thus I can only conclude that the project got larger or more complicated. (Altho it’s also possible that the underlying analyzer got smarter, thus requiring more resources.)

As to why you see this in some projects and not others, well… not all projects are the same. Some fit under the threshold. Others don’t.

 
HTH,
Ann

8

Thanks for the clarification.

Following your suggestion, we’ve enabled SonarCloud scans through CI checks. However, we’re now encountering an issue: when there are code changes in a PR, the SonarCloud scan gets stuck during analysis. The logs repeatedly show:

INFO 1/2 source file have been analyzed
INFO 1/2 source file have been analyzed
…
This continues indefinitely without completing the scan.

Also for master branch, sonarcloud scans get stuck with following:

09:22:40.394 INFO ------------- Gather SCA dependencies on project

09:22:40.707 INFO Checking if SCA is enabled for organization digitalroute

step:2:1433)09:22:40.965 INFO Dependency analysis skipped

09:22:41.020 INFO SCM Publisher SCM provider for this project is: git

09:22:41.023 INFO SCM Publisher 18 source files to be analyzed

09:22:51.025 INFO 12/18 source files have been analyzed

09:23:01.025 INFO 12/18 source files have been analyzed

09:23:11.026 INFO 12/18 source files have been analyzed

09:23:21.026 INFO 12/18 source files have been analyzed

9

Hi,

We try to keep it to one topic per thread. Otherwise it can get messy, fast.

I believe you’re encountering what’s detailed in this thread, which contains a workaround while we work on the fix:

If you have further questions about this, please join that thread or create a new one.

 
Ann