-
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
Support BitBucket Server api v1.0 #10
Comments
I think so too but I did not know whether that Bitbucket Server use V1 interfaces still. |
It definitely does use them :( At any rate, its API browser does not list v2. Possible to check via Atlassian sdk; that allows an instance to be spun up locally. |
Oops. but thank you for your information. |
I had to create a plugin recently and used https://developer.atlassian.com/docs/getting-started/set-up-the-atlassian-plugin-sdk-and-build-a-project. I was able to test against the API there fine. |
Oh looked closely, it is need to use jdk, it's heavy 😢 . |
Atlassian say it's in their issue tracker, but shelved; https://twitter.com/ddbennett/status/827195762530357248. |
I'm doing some work on this internally, and will PR it once I'm through. |
I discovered that BitBucket Server does not support the v2.0 API that bitbucket.org does.
One could add this via 1-suffixed functions, for example on PullRequests:
Or one could make a new struct, like
PullRequests1
and inject that into the client, soclient.Repositories.PullRequests1.Blah(...)
would be the calling code.Or I think it would be possible to parameterise which API version being used (probably when creating the client), and then use that to key into a map of url-generation funcs.
Would you be open to PRs that add v1 APIs? If so, by which means of the above, or another?
Alternatively, I'd love to find out I'm wrong about BB Server only exposing v1.0...
The text was updated successfully, but these errors were encountered: