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

Better Bitbucket DC webhook configuration

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Data Center, Webhooks
    • None
    • 7
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      My main intention of the Webhook configuration is to trigger a build if

      • A Pullrequest is opend
      • The source branch has been updated
      • The target branch was changed
        A build shall NOT be triggered if
      • Reviewers updated
      • Description / title of the PR changed

      to save resources and to prevent unwanted merge blocker if a successful build is need (e.g. we have build durations > 2h and the merge is blocked due to the rebuild in case of reviewers / description update)

      To get as close as possible to this setup I use the following configuration
      See

      Now I have the following bug / feature request:

      1. BUG:
        If I add / remove a reviewer, a Webhook is fired although the “Reviewers Updated” Option is deactivated. It is fired due to the enabled modified option. But according to the description and the existence of the ‘Reviewers updated option’, a WebHook should not be fired.
        This should be corrected. If there is an explicit option to fire Webhooks in case of reviewers updated then the Modified option should not fire a Webhook in this case.
      1. Feature request:
        “Modified Option” triggers a Webhook if the description, the title or the target branch is changed. This shall be splitted into two options: “Target branch changed” and “PR title/description changed” to prevent unwanted builds when changing the description/ title and to build the SW in case of target branch changes.

      I hope that both can be fixed/implemented by Atlassian. Thank you for your help.

              Unassigned Unassigned
              5652b534653d Thomas Beck
              Votes:
              4 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: