How to force all steps to pass before merge

[Łukasz Naporski]

Hi,
i looked through the available merge checks and did not find any option to require further steps from the pipeline. I would like the merge option to be available after completing all pipeline steps. Any suggestions?

[Saxea _Flowie_]

@Łukasz Naporski 

Right, so Bitbucket doesn't have built-in support for this feature. However, you could try to work around this by initially creating a pending build status with the commit status API, and then updating that status in the third step of your process. Also, set the minimum builds to two. 

Alternatively, we're planning to introduce a feature in Flowie, our Bitbucket add-on, that will allow you to easily specify checks like this for your pipelines, along with the other existing checks, in the near future which could be helpful too!

#sorry, meant to reply this on the thread below.

[Saxea _Flowie_]

Hi @Łukasz Naporski ,

Isn't the "Minimum number of successful build for the last commit with no failed builds" what you are looking for?

[Łukasz Naporski]

Unfortunately this option won't work this way. Despite setting the requirement for 3 successful builds, it did not bring the intended effect

[Saxea _Flowie_]

Oh, think I see what you mean... Is it marking the build as passed once the first step is run, not necessarily when it completes all the steps in the pipeline? You have manual steps?

[Łukasz Naporski]

I would like to force the passage of a minimum of 3 of the 4 steps. So that the ability to merge a feature would only be available after passing the 3rd step minimum