I recently came across a PR build which for some reason was only checking if code merge is possible and was not really building on merged code.

I always had an understanding that the PR build should do following (assuming a feature branch is being merged to master)

  • checkout the destination branch (master)
  • pull/merge the source branch (feature)
  • make sure merge has no issues [OR Fail]
  • trigger necessary steps of build i.e. compile, test etc.
  • clean up

I tried searching on internet on what are the steps followed during PR build but could not find anything clear. I wanted to check with this community if this understanding is correct OR I had a wrong understanding of PR builds all along.


We are using Bitbucket Branch Source Plugin

  • this depends quite a bit on what plugins you are using. can you update the question with this information please? Sep 5, 2022 at 6:21
  • @BruceBecker Updated the same
    – dev2d
    Sep 6, 2022 at 3:09
  • I don't think we can tell you what that specific "build" is for. Here's a contrived reason it might exist: Suppose someone creates a PR into master without issues and leaves it open. A few hours later someone else completes a PR into master that now causes the first PR to have conflicts. This "build" could run, see that the source branch can no longer be merged cleanly into master, and notify someone that the PR source branch needs updating. Not all "builds" need to actually "build" something. You could have 5 different "builds" pointing to the same PR, all doing different things.
    – TTT
    Sep 7, 2022 at 19:12
  • @TTT my question was more of.. What is the purpose of the PR build? How different teams are using it? Is my understanding above correct when it comes to the core purpose of PR build?
    – dev2d
    Sep 9, 2022 at 1:29


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Browse other questions tagged or ask your own question.