-
Notifications
You must be signed in to change notification settings - Fork 72
Bitbucket API changed #107
Comments
We have the same problem :/ |
Compiling from sources and replacing currently installed version resolved an issue :) |
We got the same issue |
I have fixed this problem by re-build the source code. Cause the bitbucket api v1.0 is not support. I have upload the release *.jar in my forked repo. You can get the jar in Sonarqube Plugin V1.3.0 |
@mrueegg can you publish releases on this project please? I keep having to build jars for fixes and if I have to do this for the third time might have to automate it on my fork 😿 |
Same here. |
1 similar comment
Same here. |
Hi guys, any plan to update this? :) |
Hello @Soyn, Any change of you create a PR in this repo? If not, could you please provide us the commit where you changed it so we can replicate here? |
Just clone the repo, then build the source code follow the readme. The latest release in this repo is using v1 api. But in the current codebase. The code use the v2 api. There would have no change in the source code. More info in sonar-bitbucket-plugin/src/main/scala/ch/mibex/bitbucket/sonar/client/BitbucketClient.scala Line 113 in 440555f
|
@ariellyciandt Hope it is helpful. |
Hi @Soyn , actually we did that but I believe that it's not the official way, since we initially downloaded the plugin through Marketplace. As you can see on the image bellow it's using the 1.3.0 from your repo, but it would be great to use the official version. Does anyone have plan to release the official plugin? The latest release is from Dec 18,2017. I think that question is more for the sonar-bitbucket-plugin developers. Thank you, |
From yesterday integration with bitbucket is not working. In logs we can see:
ERROR: Error during SonarQube Scanner execution
08:34:06 ERROR: POST https://api.bitbucket.org/1.0/repositories/XXXXX/pullrequests/922/comments returned a response status of 410 Gone
08:34:06 ERROR:
08:34:06 ERROR: Re-run SonarQube Scanner using the -X switch to enable full debug logging.
Going to this endpoint gives us message:
The text was updated successfully, but these errors were encountered: