Pull Request Failure

Template for a good new topic, formatted with Markdown:

  • ALM used: Azure DevOps

  • CI system used: Azure DevOps

  • Scanner command used when applicable (private details masked)

  • Languages of the repository: C#

  • Private SonarCloud project

  • Error observed (wrap logs/code around with triple quotes ``` for proper formatting)
    Caused by: Could not find the pullrequest with key ‘32359’
    Caused by: org.sonarqube.ws.client.HttpException: Error 404 on https://sonarcloud.io/api/alm_integration/show_pullrequest?project=xxx&pullrequestKey=32359 : {“errors”:[{“msg”:“Unable to find the pullrequest with key \u002732359\u0027”}]}

  • Steps to reproduce
    we fire off our PR’s through Azure DevOps CI/CD pipeline - no changes were made and it started failing at 3pm EST on 3/26

  • Potential workaround
    None that we know of

Hey there.

Have you checked to see if the token set at the Organization level is still valid? (global Administration > Organization settings)

You can also check if you have something configured at the project-level: (Project-level Administration > Pull Requests > Integration with Azure DevOps Services > Personal access token).

Typically when main branch analysis works but PR analysis fails, this is the culprit.

Yes, we not only verified the organization level token validity, but also tried running with a PAT on just the one project to no avail.

The error message is attached

we found the problem based on this - thanks for the help

1 Like