It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Can I trigger Bitbucket pipeline with pull request?

Normally the pipeline is triggered by push. There is the possibility to configure an 'on pull request' webhook, but how to connect it with a pipeline and disable or reconfigure the default 'Pipelines' webhook which triggers on push?

12 answers

1 accepted

5 votes
Answer accepted

Hi Brain, will it be triggered when a PR is merged/closed? 

No; it will be triggered when a PR is created or updated (the source branch of the PR is pushed to).

When it is merged, the relevant pipelines on the target branch will run, if they are configured.

For example, I configured my pipelines to run tests on pull requests, and on the master branch. So when I merge a pull request to master, the tests run on master because of the configuration of master, not because of the configuration of the pull requests.

Like # people like this

good to know, thanks! 

I deploy PR's to an environment for integration tests, and looking for a way to clean up resources when a PR has gone... 

Like Jordi Bassaganya likes this

Hi Brian, there's any way to have the source and destination branch?

In branch' triggered pull requests I have the BITBUCKET_BRANCH that allow me to execute some script in order to run some code, but not in PR triggered pipelines.

 

Edit: with this line you can have the origin branch

export BRANCH=$(git branch | grep \* | cut -d ' ' -f2)

 

You can get the destination branch with the BITBUCKET_PR_DESTINATION_BRANCH variable

https://confluence.atlassian.com/bitbucket/variables-in-pipelines-794502608.html

Thank you. This is _very_ important for me. I run a team of 3 developers and contractors that float in-and-out. We manage a dozen repos and quality-checking is a big issue for us. In addition to manual code-reviews, making sure all tests run as the PR is created or updated is one less step I need to take. 

Like Ashvin Narayanan likes this

@Brian_Maissy In the documentation it reads "When it's triggered, we'll merge the destination branch into your working branch before it runs. If the merge fails we will stop the pipeline."

So is my understanding (below) correct:

  1. It won't get to the pipleline steps if the merge fails
  2. The Pull Request will be created regardless, but would have the usual warning sign next to the Merge button that informs about conflicts

If this is indeed the case, how do I execute steps on merge failure?

Is  after-script applicable here? 

Yes, I think your understanding is correct.

I'm not sure if the after-script will run or not in that case; I would just check and see.

Yeah, I would love this feature. The ideal workflow in my mind is to have the build pass as a requirement before merging the Pull Request. This keeps your deployment branches clean. After the PR is merged, the current feature set is nice to watch master/development branches and deploy them as changes are made (ie PRs are merged).

Actually, never mind that - a search reveals no current issue open on the subject, so I created one:

https://bitbucket.org/site/master/issues/15771/run-pipelines-on-pr

please vote it if you'd like this feature.

Thanks.

So the idea here is that instead of running your pipeline on every push you run it on every PR creation?

Is it not more convenient to build and test your code ASAP?

Update: I have funnelled the feedback about the expense of up to date deploys back to the Bitbucket Pipelines team.

yes, you are right, it is more convenient to test code ASAP but for a small private or open source project you quickly run out of your 50 minutes if you build on every push.

Like # people like this

Exactly @Jan Steinke. Developers on any team should be encouraged to push their branches to remote often, even before raising a PR, without worrying about consuming build minutes on unnecessary builds. They can add [skip ci] to commit messages, but will often forget to do so.

+1 for this feature, and exactly for the reasons stated above.

If someone has made a feature request, could you please post the link, so we can upvote it?

This. It's a bit short-sighted to assume that every team has enough money for 'unlimited' build minutes. 

Like Jeremy Stafford likes this

@Robert_Massaioli__Atlassian_ The points mentioned above are nice but I'd like it for my deploy section. I want everything in master to be deployed automatically. If I merge a PR, this is new code that I need deployed.

Like Kye Russell likes this

Build everything = $$. Plus there may be times where I only want to perform certain actions on a PR but not a typical feature branch push. For example, when Joe is checking in code to remote feature branch for the weekend, I don't necessarily want to burn build time running static code analysis on incomplete code, but on a PR, I absolutely do.

Like Kye Russell likes this

This sort of ignorance of financial factors is the same sort of thinking that causes Atlassian to think that it's appropriate to skyrocket their Jira seat price if I dare wish to enforce on Two Factor Authentication for my users.

I digress.

3 votes

Hi Marian,

At the moment it is not possible to trigger a pipeline on a pull request being created. However, pipelines run on the source branch will be displayed along with the pull request. If this is something you would like in the product please create a feature request at https://bitbucket.org/site/master/ telling us what you'd like in this feature. 

I needed to trigger bitbucket pipeline for every created pull requests. As this is not available by default, I've managed to do it with a simple zapier zap, here is the tutorial :
https://medium.com/@kyann/how-to-launch-a-bitbucket-pipeline-on-pull-request-creation-aka-launch-sonar-on-pull-request-efc7e93679fc

Hi,

Is it possible to rerun the pipeline of the merge when the pull-request is updated? We want to require at least two successful builds without failed builds. One for the last commit itself, and one for the potential merge.

What I've observed is that a change in the pull request will reset the "successful build counter" and will initiate a new build on the new commit (we have it setup to build on each commit), but will not trigger a new build on the potential merge. Is there currently a way to achieve that?

Thanks,

Fred

Nevermind, it seems that I mislabeled the branch that I want this to affect in my yml.

By changing:

pull-requests:
develop:

to

pull-requests:
    '**':

It now works. I can't seem to make it work for a specific branch. Is there a special format?

I tried:

develop
origin/develop
*develop*
develop*
*/develop

And none of these work.

Like Mzwandile_Shandu likes this

It would be, but when we start having to pay for minutes to build, I think I will want this feature too. That way I could setup pipelines to only run tests on the master branch, and if anyone creates a pull request to the master branch, those also get run through pipelines. This might help save some minutes.

totally agree with you. Just for info, there is a cache feature now that should save some seconds on each pipeline run. 

We also want to have this feature and came up with a workaround outlined here: https://bitbucket.org/site/master/issues/13438/add-specific-pipelines-configuration-for#comment-40276332

as a workaround, you can push an empty commit

Is it possible to skip pipelines, or to prevent it to not failed when there is a merge conflict on the pull request

0 votes
Eduardo I'm New Here Jan 30, 2020

I have a Jenkins pipeline to increase the version number of my artifacts automatically, what it does is:

  • Clones DEV branch
  • Changes the version number
  • push the changes(user is Jenkins)
  • creates a pull request on BitBucket repository
  • Once the pull request is approved, is merged.

My question is: Is there some way to indicate BitBucket if a Pull Request comes from a particular user (in this case Jenkins) to auto approve immediately or not request any approver to merge?

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket

Bitbucket Server 7.0 is here!

Hello Community, I’m Anton Genkin, a product manager on the Bitbucket Server and Data Center team and am excited to share that Bitbucket Server 7.0 is now available! It's a platform release, one th...

989 views 6 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you