How to prevent pull request metadata updates from triggering CI builds (BCLOUD-21184)

Question

Hi Atlassian Support Team,

We are currently using Bitbucket Cloud and have a webhook configured to trigger our CI/CD pipeline (AWS CodeBuild) whenever a pull request is updated.

The issue we are facing is that the pullrequest:updated webhook fires for every single metadata change on the PR—such as updating the title, modifying the description, or adding/removing reviewers. Because we rely on PR events to build new ECR images, these metadata-only webhooks are triggering unnecessary CodeBuild runs, which wastes compute resources and increases our AWS costs.

I understand that in Bitbucket Server and Data Center, this problem was resolved in version 7.0 by introducing the "Source branch updated" trigger (BSERV-10279).

I also see there is an open feature request for Bitbucket Cloud (BCLOUD-21184) to introduce a pullrequest:push webhook type that specifically triggers only when new commits are pushed to the source branch of an open PR.

Could you please clarify:

* Is there any native configuration or workaround within Bitbucket Cloud to filter out metadata updates from the webhook payload before it is sent?
* What is the current timeline or ETA for the release of the pullrequest:push webhook mentioned in BCLOUD-21184? Is there an early access or beta program we could join?

Thank you for your help!

Arkadiusz Wroblewski · Answer

Hello  @Pranay Kumar Polishetti

Keep an eye on

[BCLOUD-21184] Webhook trigger for Pull request commit - Create and track feature requests for Atlassian products. for native webhook support, but implement the repo:push workflow in the meantime to avoid burning CodeBuild resources on PR description updates.

Best,

Arek 🤠

Mihai_LeanZero · Answer

Not natively, as far as the docs go. The pullrequest:updated payload has no changes object, so a title edit and a new commit look the same.

CodeBuild can't split them either. Its filter types (EVENT, ACTOR_ACCOUNT_ID, HEAD_REF, BASE_REF, FILE_PATH, COMMIT_MESSAGE, WORKFLOW_NAME) treat PULL_REQUEST_UPDATED as one event.

BCLOUD-21184 is still In Progress. Atlassian's 2024-08-19 note says they're adding pullrequest:push, but there's no ETA or beta published, so vote and watch it.

Meanwhile, something to try (haven't run it myself): point the Bitbucket webhook at a small Lambda instead of CodeBuild's own, have it compare pullrequest.source.commit.hash with the last one seen for that PR (DynamoDB or similar), and only call StartBuild when it changed. Does the webhook go straight into CodeBuild today?