Rolling builds per workflow

Description of the feature request

I manually started BitriseCacheRefresh. Then a pull request opened that triggered RunUnitTests. I expected both of these workflows to run in parallel. Instead BitriseCacheRefresh was cancelled via rolling builds.

Use case / for what or how I would use it

I’d like the ability to cancel rolling builds per workflow. If I have two unrelated workflows, then they shouldn’t cancel each other out.

I don’t think manually created jobs or scheduled jobs should be aborted.

BitriseCacheRefresh is starting the RunUnitTests job to populate the cache. That job then cancels the BitriseCacheRefresh job. There’s no way to start a job on bitrise and prevent it from cancelling other jobs. :sob:

Hi @bootstraponline,

I believe this is a duplicate of Do not cancel builds on same branch if another workflow is triggered

Can you please check it and let me know if that covers your use case / if I can close this one?

1 Like

Yep, looks like a duplicate.

1 Like

Closing it here - please vote & comment at Do not cancel builds on same branch if another workflow is triggered to bump its priority! :slight_smile: