We’re using resource groups to ensure that our integration test job doesn’t run during a deployment (it would probably fail! yes we should get zero-downtime-deployments sometime…).
Everything is working as I expect, but this is more constraining that it needs to be:
There’s no reason multiple test jobs couldn’t run concurrently, it’s just that a deployment should never run during a test, or another deployment.
This is similar to the situation in database with reads and writes: Many reads can happen at once, but writes shouldn’t happen concurrently with anything else.
Our experience with testing would be a lot better if we could run the tests concurrently, while still making sure tests and deployments are not concurrent. Is that possible with resource groups, or some other way?