Merge checks: Ensure all build are passing

[Dave Weber]

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?

[Ulrich Kuhnhardt _IzymesCo_]

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 https://jira.atlassian.com/browse/BCLOUD-19885 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!