Could not find the pullrequest with key '208'

Task 'sonarqube' is deprecated. Use 'sonar' instead.

> Task :sonarqube FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':sonarqube'.
> Could not find the pullrequest with key '208'

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.2/userguide/command_line_interface.html#sec:command_line_warnings

Execution optimizations have been disabled for 1 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.

BUILD FAILED in 5m 48s
224 actionable tasks: 220 executed, 4 up-to-date

Publishing a build scan to scans.gradle.com requires accepting the Gradle Terms of Service defined at https://gradle.com/terms-of-service. Do you accept these terms? [yes, no] 

The build scan was not published due to a configuration problem.

The Gradle Terms of Service have not been agreed to.

For more information, please see https://gradle.com/help/plugin-terms-of-service.

Alternatively, if you are using Gradle Enterprise, specify the server location.
For more information, please see https://gradle.com/help/plugin-enterprise-config.


Exited with code exit status 1
CircleCI received exit code 1

This is the error I am getting after when the sonar command is triggered.

I have deleted the project on sonar, created it again, input the new token across circle CI, bitbucket created a new branch and created the PR but still to no avail.

Hey there.

What DevOps paltform are you using? (GitHub, Azure DevOps, Bitbucket, Gitlab…)

I use Circle Ci for DevOps and bitbucket houses my source code.

@Colin

Any thoughts please

Hey there.

Are you still facing the issue? If you can run the analysis in DEBUG mode (--debug), I’m happy to open a private channel to share the logs.