Pull Requests run tests as part of merge process.

[Timothy Holtom]

I have writte a set of system tests in a repo designed to execute against an external application. When I try to merge my tests into the repo, the pipeline process thinks I am checking in application code and runs the system tests, as if they were tests designed to test application code in the same repo.

Is there a way to have the pipeline not execute the tests automatically on a merge? Is there a flag? Or configuration option? There is the [skip ci] option for the commit message, but I don't want to skip the whole pipeline job, just the tests.

Any ideas?

[Aron Gombas _Midori_]

You can set up multiple pipelines in the same Bitbucket Pipelines config YAML with different triggers.

You could solve this problem as simple as moving your "system tests" to a second, non-default, custom pipeline.

That way, commit, PR merges would still trigger your tests that test the codebase, but they wouldn't trigger the system tests. (You can start those manually any time!)

[Saxea _Flowie_]

Hi @Timothy Holtom

I think changesets might be useful to what you are trying to achieve. Another option, would be to let your build tool handle that, and know what to execute based on what files were changed.

We also provide further control on when and how pipelines are triggered using Flowie, Bitbucket cloud app via smart pipelines plugin. You can use different conditions on your PR to set an environment variable and then you pipeline or build tool can use it to determine what do execute.