Ok, let me try to put a bit of context here:
Why are we using a "custom" BB Server plugin for webhooks?
Because when bb-branch-source development started there were no built-in webhooks support in BB Server. However BB Cloud already had it. So the most sensible solution by that time was to use a plugin in BB Server to somehow "mimic" webhook messages from BB Cloud. That way the same code could handle webhooks from both BB Server and BB Cloud.
The "official" plugin, as many of you already said, is: https://marketplace.atlassian.com/plugins/nl.topicus.bitbucket.bitbucket-webhooks/server/overview - which is OSS and the code is on GitHub: https://github.com/Eernie/bitbucket-webhooks-plugin
BB Server comes with built-in webhooks now
Yes. And that's causing confusion, sorry for that. I'll try to write fresh and clear docs on this in the short term.
In the long term we have to decide what to do about this. Options are:
1. Support both webhook types (plugin generated and built-in)
2. Support built-in webhooks only
3. Support plugin webhook only
Each options has pros and cons:
1. Supporting both has significant maintenance overhead
2. Supporting built-in only will probably break most of existent setups, and we would lose any control over the evolution of the webhooks source (the current plugin is OSS, actively maintained and accepting contributions).
3. Supporting plugin webhooks only, it seems to be producing confusion and installing a plugin is not always well-seen (specially on rigid BB Server installations) when there is a built-in alternative.
IMO, until BB Server webhooks are "compatible" with BB Cloud webhooks payload we should stick to the "custom" plugin approach.