How do you configure the "Require multiple successful builds" merge check to actually build the code

[smmathew]

I have read the documentation on merge checks but so far in BitBucket this just looks like a simple on/off choice. Where/how do you actually tell the system what a build is and how to execute it?

[Caterina Curti]

Hi @smmathew,

Which Continuos Integration tool are you connecting to Bitbucket?

For example, if you are connecting the self-hosted version of Bitbucket with Bamboo, you can configure a build to be triggered for every push to a repository.

The build status will then be sent back to Bitbucket and can be used as Merge Check.

More details on how to connect Bitbucket Server with Bamboo are available on the Integrating Bamboo with Bitbucket Server page.

For a step-by-step guide, you can also check the How to connect Bamboo and Bitbucket Server page.

If you are using Bitbucket.org (hosted by Atlassian), the Bitbucket Pipelines page would be a good starting point.

Cheers,

Caterina - Atlassian

[smmathew]

Thanks for the info Caterina. 

I am using Jenkins to build the application. I have gotten to the point that I can commit code and it will trigger a build whose status shows up back in BitBucket so that is good. 

I am however seeing some odd behavior. The scenario is that I have a pull request that contains 3 commits. 2 of the commits are successfully built, and 1 is not. When I create the pull request it shows 1 unsuccessful build. If I wait a few seconds and refresh then it will show all commits as successful. Is there any reason that this should happen?

-Steven