Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-14136

Webhooks PR target branch updated event floods queue causing events to get dropped

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • 8.8.0, 8.9.1, 8.10.0
    • Webhooks
    • None

      Issue Summary

      This is reproducible on Data Center: yes

      The PR target branch updated webhook event will trigger an individual webhook request for each individual PR targeting the updated branch. For medium-large repositories with a decent number of PRs targeting the same branch (e.g. master) this has the potential to flood the webhooks queue each time the given branch is updated. This is causing a large number of webhook requests to get dropped frequently.

      Due to performance concerns, we have disabled the event and back-ported it to all affected versions. Ticket will remain open until a long-term solution is implemented.

      Expected Results

      All webhook requests are sent successfully.

      Actual Results

      A large number of webhook requests are getting dropped from the queue and hence, are not being sent.

      Workaround

      Depending on the use case, the PR merged event can be used as an alternative event by checking the target branch in the payload. If the PR merged event does not work for your use case, there is no current work around. 

            [BSERV-14136] Webhooks PR target branch updated event floods queue causing events to get dropped

            When will this be resolved?

            We really need a resolution or a robust workaround.

            Joe Johnstone added a comment - When will this be resolved? We really need a resolution or a robust workaround.

            If the branch update does not trigger a build via webhook on external CI and the Developer never finds out about his broken code, then that can delay his PRs for days. It is not a minor problem.

            Edgars Batna added a comment - If the branch update does not trigger a build via webhook on external CI and the Developer never finds out about his broken code, then that can delay his PRs for days. It is not a minor problem.

            Any update here? Is there a workaround? Is it possible to enable the feature with a flag?

            Stephan Krull added a comment - Any update here? Is there a workaround? Is it possible to enable the feature with a flag?

            Nitin Sharma added a comment - https://getsupport.atlassian.com/browse/SSP-57278

              Unassigned Unassigned
              8f36004e07e8 Milly Wilson
              Affected customers:
              5 This affects my team
              Watchers:
              11 Start watching this issue

                Created:
                Updated: