Multiple unrelated builds showing for a PR

[David Connack]

Hello

I have a situation where I want to automate creating prs to some branches when a merge is done to main.
I have pipelines that run on prs.
Im seeing all the pipelines for all the builds on all the prs.
So if I have 4 prs, I am seeing 4 builds on each pr instead of 1 each.

If one of the builds fails, it blocks all the prs.

I found this thread that seems to indicate why:

For commit statuses to show on the pull request page the following criteria needs to be met:

• the commit has of the commit status matches the current commit has of the source PR branch

• if the commit status refname is null or it matches the branch name of the source branch.

How can I prevent the other prs build from appearing on each-others prs

[Katarína Lukácsy]

Hi David!

I'd love to help you achieve your goal but first please allow me to better understand some specifics about your cofiguration.

First off, what type of pipelines do you run on your PRs? Please refer to this blogpost in case my question is confusing. I would like to know if you run `branches` or `pull-request` pipelines. 

https://bitbucket.org/blog/level-up-your-code-review-with-continuous-integration#:~:text=Branch%20pipelines%20are%20triggered%20every,pull%20request%20has%20been%20created.

Second, would you mind telling me in more detail what source and destination branches you use when you auto-create your PRs? I'd like to understand which, if any, of the two types of branches those PRs share.

Thanks,

Katarina

[David Connack]

Hey Katarína

These pipelines are pull-request piplelines:
It looks like this:

pipelines:

pull-requests:

'**':

 - step:

name: Run tests

size: 2x

oidc: true

caches:

 - docker

 - gradle

script:

 - bash ci/scripts/test_ci.sh

services:

 - docker-4g

We have 4 dev branches called dev-0, dev-1, dev-2, dev-3.
The prs source is main, and the destination are the above dev branches.
They all share the above pull request pipeline.