Something went wrong while trying to get the pullrequest with key '130'

I have seen 29939 and 137100 which seem to be the same error. I have also taken a look at other thread posts with the same issue but no clear solution. Is a solution available for this problem?

Neither sonarqube-scan-action@v7 or sonarqube-scan-action@v6 seem to work in the GitHub Action.

The project uses TypeScript and the repository is public.

Repository
PR
Action Logs

I don’t see any documentation mentioning any special treatment or anything related to this error. I have also tried uninstalling and installing SonarQubeCloud.

The action output shows:

...
02:01:58.453 INFO  Load project pull requests (done) | time=321ms
02:01:58.456 INFO  Load branch configuration
02:01:58.457 INFO  Github event: pull_request
02:01:58.462 INFO  Auto-configuring pull request 130
02:01:58.807 ERROR Something went wrong while trying to get the pullrequest with key '130'
02:01:59.129 INFO  EXECUTION FAILURE
02:01:59.130 INFO  Total time: 9.093s
Error: Action failed: The process '/opt/hostedtoolcache/sonar-scanner-cli/7.2.0.5079/linux-x64/bin/sonar-scanner' failed with exit code 3

GitHub CI/CD yaml:

name: Test and SonarCloud analysis

on:
  push:
    branches: [ main ]
  pull_request:
    branches: [ main ]

jobs:
  test-and-analyze:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v6
        with:
          fetch-depth: 0

      - name: Setup pnpm
        uses: pnpm/action-setup@v4
        with:
          version: 10.9.0

      - name: Use Node.js
        uses: actions/setup-node@v6
        with:
          node-version: '20'
          cache: 'pnpm'

      - name: Install dependencies
        run: pnpm install --frozen-lockfile

      - name: Run tests and generate coverage
        run: pnpm run test:coverage

      - name: SonarQube Scan
        uses: SonarSource/sonarqube-scan-action@v6
        env:
          SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}

I have also tried adding the GITHUB_TOKEN to the environment, but the same error is produced.

Hi,

Can you add

args: -Dsonar.verbose=true to your scan action and post the log here, redacted as necessary?

 
Thx,
Ann

Hello,

Sorry for the long reply!

I’ve ran the following via GH CI/CD:

- name: SonarQube Scan
  uses: SonarSource/sonarqube-scan-action@v6
  with:
    args: >
      -Dsonar.verbose=true
  env:
    SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

The GH run can be found here.
At a glance it seems like an exception is thrown and propagated, as the sonar cloud API returns a 500.

Hi,

Thanks for that. Here’s a synopsis:

I can’t go a lot further; I’m going to flag this for the team.

 
Ann

Hi again,

I just want to let you know that this is not forgotten. The investigations on our side are ongoing.

 
Ann

Hi @Supermarcel10,

Sorry for the waiting time. I’ll be looking into your issue and first I’d like to understand your usecase a bit better. I see you already have a successful SonarQube analysis in another PR. What is this job lacking for you to try to set up a SonarQube analysis manually in a GHA workflow?

Thank you!

I see you “have also tried uninstalling and installing SonarQubeCloud”, but your SQC organization is “Not bound”. What did you with the SonarQubeCloud app the last time? Did you uninstall or install it?

Can I ask you to bind your SonarQube Cloud organization and then try to run the `test-and-analyze` GitHub Action again, please?