-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reg : REST API endpoint to v2 #199
Comments
@nishio-dens the latest version of the plugin (V 1.4.30) is pointing to REST API 1.0. I tried using the older version (V 1.4.28) & it is calling API 2.0 . Please make the changes in the latest version of the plugin as well. |
The only portion of the pullrequest builder that speaks v1.0 is the STASH implementation. Please let me know if you're using stash, or what v1 endpoint is being used. |
This is the configuration that I have done from my end with v 1.4.28(the plugin is working as expected). I am not sure whether I have used any STASH or not. please let me know how to check it or share a link where I can have more understanding about stash. |
You have obscured the only field that would let me know. If you are using stash, then your url will not contain However, the second part of my question was more important: Why do you think that v1 endpoints are being used? |
Yes , my URL starts " https://[email protected] " In the logs i could see that URL for which the call is made . PFA the screenshot. |
That is strange -- I'll look into it ASAP. |
Check your Bitbucket URL field - should be empty for bitbucket cloud. |
I am currently having bitbuckrt-pullrequest-builder-plugin V 1.4.30. The plugin is currently calling REST API version 1.0. Is there any configuration which I can change to make the plugins call REST API 2.0.
This issue was discussed in #160 as well , but it is not mentioned whether the configuration change has been done or not.
The text was updated successfully, but these errors were encountered: