Is it possible to prevent certain jobs running concurrently?


I have some jobs in my config that access the same remote resource and that creates a data race. Can I somehow prevent these colliding jobs running concurrently within one build? Or maybe I can forbid all jobs running concurrently? Is it possible to forbid running jobs concurrently across multiple builds?

Notice, that I’m talking about jobs and not steps.

if you’re using workflows, you can just ensure the second job requires the first job so that it happens sequentially.

not sure how to prevent the same job from running on two different workflows unless you only have a 1x concurrency set on your account.