One time run of Bit bucket pipelines.

Question

Hello Team,

I have a scenario where, I need a merge check where the pr's shouldn't merge with out this test plan run successfully.

But apparently this test plan cannot be run into every commit, because this will run for about 45~50mins on an average.

But we cannot deploy our changes into production without running this test plan.

Is there any way, where we can customise the running pipeline or any other resoruces/ ways, where we can make this run only once before we merge the pipeline ?

Or any other ways do you guys suggest ?

Thanks - Arun Kumar D

Saxea _Flowie_ · Answer

Hi @Arun Kumar D,

We provide Flowie, a Bitbucket Cloud app, built specifically for this kind of workflow. It's a common setup, since teams often want to hold off on long or expensive tests until later in the PR lifecycle.

With Flowie, you can use labels to control when those tests run. Many teams use something like Status: Ready to merge or Status: Integration tests. Once that label is added, Flowie triggers the CI pipeline for the long-running tests.

Some users also use draft PRs to hold off builds until the PR is ready, or set up rules like requiring a minimum number of reviewers - all fully supported by Flowie.

If the long tests fail, Flowie will automatically re-trigger them on the next commit, as long as the label is still present.

You can also set up Flowie’s built-in merge checks to make sure the PR only merges or deploys once all checks pass. And with Flowie's unique smart auto-merge feature, it can merge PRs for you - no need to constantly watch and monitor the checks and press merge.

If you'd like to try Flowie, we can assist you tailoring your configuration to your specific needs, just reach out to us at support@flowie.app. We can help you make the most of Flowie and fully automate your workflow.

Arun Kumar D · Answer

Thanks Aron for the manul help.

Can you also help me that forge app what to do?

Aron Gombas _Midori_ · Answer

It is not available as a 100% automatic feature, but there is an easy workaround that requires a little discipline and manual effort from you.

Manual workaround

You can configure a custom manual pipeline:

pipelines:
  custom:
    before-merge-check:
      - step:
          name: "Run Pre-Merge Tests"
          script:
            - echo "Running tests before merge..."
            - ./run-tests.sh

Then you would:

Go to the PR

Run the before-merge-check custom pipeline manually

Wait for it to pass before clicking “Merge”

Automatic solution

Or, even better, you can develop a custom merge check as a Forge app! The merge check could run the pipeline and allow/disallow the merge based on the pipeline result.