Pull request pipeline is not triggered on merge commit via BitBucket

[Robbe Sneyders]

Problem description

In our bitbucket-pipelines, we define a pipeline to run on a pull request for every `feature/*` branch.

We open a pull request to merge branch `feature/A` into master, and pipelines are triggered fine for every pushed commit.

Since feature A is a very big feature, a coworker decides to help, and branches of `feature/A2` from `feature/A`.

Feature A2 is ready, so we decide to merge `feature/A2` into `feature/A`. This adds a merge commit on top of `feature/A`, but a pipeline is not triggered.

Now if I merge `feature/A2` into `feature/A` locally, and then push the merge commit, the PR pipeline does trigger.

Expected behavior:

A pipeline is triggered for every change in the source branch of the PR.

Actual behavior:

A merge via BitBucket into the source branch of an open PR does not trigger the pipeline registered for that PR.

[Daniel Santos · Accepted solution]

Hi @Robbe Sneyders

Thank you for sharing the detailed description of this scenario.

I was able to reproduce it like you described and used your description to create a new bug [#19094] - Cascaded pull request does not trigger pipelines as expected on UI merge.

We will now need to wait for our developers to triage it and prioritize its resolution according to our Bug Fix Policy - Atlassian Documentation.

I'm afraid you will need to use the workaround you described while this is not fixed. In case you need to have cascaded pull requests.

Please let me know if you have other questions on this matter.

[Troy Koss]

Hi - Similar issue. If I have a pull-request on a feature/A branch into my develop branch, the commit of the code into develop does not trigger the develop commit pipeline.

[Daniel Santos]

From what I understood of your description, the build should happen in feature/A not in develop. That branch is the one with the pull request and that is what needs to be adjusted in order to merge it later into develop.

To build the develop branch you need to create a pipeline configuration there which is not related to pull requests so this build can run on new commits.