-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
Add bitbucket Server integration #10903
Comments
Hello @zulip/server-integrations members, this issue was labeled with the "area: integrations" label, so you may want to check it out! |
Hello @timabbott ! |
@santherics should this be implemented, it would work just like our other ~10 integrations for Git tools, with the same formatting/etc. as the rest. |
Hi @timabbott my organization is also interested in this functionality. We would like to see it work the same as the other Bitbucket integration except for Bitbucket Server. |
Here you can find the format sent by Bitbucket Enterprise: For example, the event key for pull request creation: and here you can find, what is sent by Bitbucket Cloud (what is already supported by Zulip): Here, the event key for pull request creation: |
This feature should be completed with PR #11992 |
For now it's been implemented much like any other webhook (zulip-writer). |
@timabbott Would we say that this issue can be closed or is there something else that we should implement (Like maybe #10907) before we can call the case closed? |
Yes, this was finished by #11992 and we can close. I do think we should work on #10907, for improving this integration and other issues, but we now have an integration and so this issue can be closed. I'd love feedback from the various users who posted on this thread; you can use |
Apparently, Bitbucket Server's webhooks are neither the same as Bitbucket Cloud (our "bitbucket2" integration) or Bitbucket Enterprise (our "bitbucket" integration). It's crazy that Atlassian manages to have 3 different formats for one product, but in any case, we should build an integration to accept requests from it.
Unfortunately, Bitbucket Server's outgoing webhooks are poorly-designed, in that they don't contain the actual details about the commits (you have to callback to the server to get those).
There's two ways we can go about making this work:
BotConfigData
) for storing the BitBucket Server API credentials needed for the callback in a traditional Zulip webhooks.I suspect the first option will end up being preferable, just because having an additional thing to deploy is no fun, but it likely also requires more design work.
The text was updated successfully, but these errors were encountered: