When you force deploy via the api controller, it sets allow_concurrency to true. So when the pipeline is unlocked and ContinuousDeliveryJob runs, it only checks for non-concurrent tasks with the current function. This means that another deployment of the same commit can be triggered by the ContinuousDeliveryJob simultaneously.
This updates ContinuousDeliveryJob so that it doesn't trigger a deploy if there is a concurrent task running.
When you force deploy via the api controller, it sets
allow_concurrencyto true. So when the pipeline is unlocked andContinuousDeliveryJobruns, it only checks for non-concurrent tasks with thecurrentfunction. This means that another deployment of the same commit can be triggered by theContinuousDeliveryJobsimultaneously.This updates
ContinuousDeliveryJobso that it doesn't trigger a deploy if there is a concurrent task running.