Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Merge checks: Ensure all build are passing

We recently configured our CircleCI to use dynamic build steps. Based on the files included in the branch, certain build steps may or may not run. For example, if we have a branch that updates only frontend code, only our frontend tests will run; if we have a branch that updates only backend code, only backend tests will run. So for Bitbucket, there are a variable number of build steps.

That causes trouble with the merge check ensuring that a certain number of builds pass. We have to set the number to be the minimum number of builds that will run each time, but for some branches, we'll have more that could fail.

Is there a way to set a merge check that all builds have passed?

1 answer

0 votes
Ulrich Kuhnhardt _IzymesCo_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Oct 31, 2021

Hi Dave,

I understand you have a variable number of builds that pass depending on the depth of code changes.

It would be good to have a configurable merge check that adjusts the number of required builds according the file paths in the PR changeset.

Unfortunately custom merge checks are not available (yet) in BBCloud despite the high interest in this feature (please vote!)

As a work-around you could define PR target branches including required builds that can be used as PR targets for backend, front-end or back+frontend pull requests. Depending on where changes are present create a PR from the feature/bugfix branch to the appropriate target branch. Then create a formal PR from that branch to develop without checking build results.

Best, Ulrich

Izymes - Remove boring from work!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events