Closed Drimix20 closed 3 years ago
@mc1arke Facing the same issue . This issue shows it's on open, any idea if there is a resolution or a merge any time soon?
Ok my issue was not using the right personal access token. Now the request is going through and I need to look into the issue with the prebuild merge commits
A change to allow logging of Bitbucket API requests and responses is included in v1.9.0 of the plugin. Please upgrade to this version and file a new issue if you can replicate the issue with debug logging.
Backported to 1.8.1 of the plugin for Sonarqube 8.9 support.
I know this ticket is closed but I'm having same issue as the original bug ticket. I set sonar.log.level=DEBUG
and am still receiving the same amount of debug logging as above Bitbucket responded with an error status (404)
. Do I need to set other analysis parameters to get further information from the ce logs?
It's the compute engine component that would generate the additional logs, so you'd want to set sonar.log.level.ce
to DEBUG
, run your attempted decoration, and then check the CE logs.
@Drimix20, @NILM1 I had the same issue and what I found is that there should be no slash at end of bitbucket server url setting
@mc1arke I think we should add check base url before sending requests to prevent //
in request url
Describe the bug During BitBucket decoration by reported issue plugin fails with exception
To Reproduce Steps to reproduce the behavior:
Expected behaviour Decorated pull request with known issues detected by SonarQube.
Software Versions
BitBucket Server v6.10.1
Can I somewhere find details about performed request?