Releases · bitrise-io/bitrise-webhooks

05 Apr 10:14

1.1.40

2eca2b9

1.1.40 Latest

Latest

Implemented bitrise.io trigger API change: trigger API main endpoint will be moved from the www. subdomain to the app. subdomain. Right now both are available but www. is deprecated.

Assets 2

13 Dec 16:08

viktorbenei

1.1.38

5020669

1.1.38

Implement Bitbucket Server provider - thanks @ChrisTitos! 🎉

Assets 2

22 Nov 16:42

viktorbenei

1.1.37

369e472

1.1.37

Bitbucket V2 webhook: allowing webhook if X-Attempt-Number is not defined.

This should allow Self-hosted Bitbucket (Server) webhooks to be processed, as reported by @majodev and the fix/change was implemented by @ChrisTitos in #66. Thank you guys! :)

Assets 2

17 Nov 17:58

viktorbenei

1.1.36

d03255a

1.1.36

Return HTTP code 200 if there was no auth or internal server error, simply the build could not be started (e.g. monthly limit reached or no trigger map entry matches the trigger), to prevent git hosting services to (falsely) auto-disable the webhook in case e.g. if you have a trigger map to only build a single branch.

As mentioned in the related README section (https://github.com/bitrise-io/bitrise-webhooks#response):

If at least one call fails:
- In case the error is not an internal error, nor an authorization or any other system error,
  just the build could not be started (e.g. Trigger Map doesn't have any mapping for the trigger),
  then the response code with be 200. This is to prevent services to "disable" the Webhook,
  as most of the git hosting services auto-disable webhooks if too many / too frequent non 2xx
  responses received.
- On the other hand, if it's a system error (e.g. an internal error or an authentication error)
  then of course the webhook server will not return a 2xx (success) code,
  but instead it'll return a 400 error with as much details in the response about the
  error as the server can determine.