Skip outdated deployment jobs cancelling jobs in the same pipeline

The “Skip outdated deployment jobs” feature documentation talks about multiple pipelines running with deployment jobs to the same environment interfering with each other. However, the feature also prevents multiple jobs in the same pipeline from deploying to the same environment.

There are two scenarios where this is a problem.

First scenario: we have sub-environments according location. For example a TEST environment will have US, EU and AS sub-environments. When we deploy to TEST we have three jobs that deploy to the sub-environments of TEST. With “Skip outdated deployment jobs enabled” only one job succeeds. For example:

image001 (1)

Yes, we could create environments like TEST-US, TEST-EU, etc. but we would prefer not to have more environments.

Second scenario: In another pipeline we build multiple products. Then there are deployment jobs to deploy each product to the same environment. With “Skip outdated deployment jobs enabled” only one job succeeds.

In both cases we would like to prevent multiple pipeline deploying to the same environment at the same time, but allow multiple jobs within the same pipeline deploying to the same environment to succeed.

Disabling “Skip outdated deployments” and using resource groups works, but it forces the deployment jobs to run sequentially instead of in parallel. For example:

image001 (2)

What do you think? Is this a bug or a feature?

Thanks,