BitBucket Server: No X-Attempt-Number Header found

[majodev]

Hi,

Looks like the BitBucket Event Payloads documentation is not completely accurate for BitBucket Server (non Cloud). The X-Attempt-Number is actually never sent. Would it be possible to apply a default value instead of an error here?

BitBucket Server Version: v5.5.1 (latest).

[viktorbenei]

We don't support self hosted Bitbucket Server right now. Are you sure that this is the only difference between Bitbucket Server's webhook format & Bitbucket.org / Cloud's? Last time we checked the difference was quite significant.

In any case, PRs are always welcome - you can find the development readme section at https://github.com/bitrise-io/bitrise-webhooks#how-to-compile--run-the-server

You can run this server on your own Mac/PC or even deploy it to a free Heroku dyno :)

If you'd have any questions just let us know! ;)

[majodev]

As far as I can tell from the payload, it's the only difference.

WebHooks v2 API Support just landed recently in BitBucket Server v5.4 and should normally work the same way as in their Cloud solution.

[viktorbenei]

Ahh, I didn't know that Bitbucket Server now supports the Bitbucket v2 API! Thanks for the heads up! ;)

I'll add this to our internal tracker, but if you'd have some time in the meantime feel free to send us a PR, it'd be very much welcome! ;)

[viktorbenei]

Released in https://github.com/bitrise-io/bitrise-webhooks/releases/tag/1.1.37

Please let us know if this indeed fixes the Bitbucket Server webhook processing issue, and thank you for reporting! :)