Due to the behavior of deployment concurrency control, when a new pipeline is started while a previous one is running, the new pipeline is paused. It would be ideal to have the ability to automatically resume the most recent paused pipeline once the current pipeline has completed.
I am aware that a paused pipeline can be resumed manually from the web interface, but having the option to start the most recent paused pipeline automatically would make the whole process a lot easier.
For example, our repo is set up to run a pipeline whenever someone commits to our development branch. If three people commit to that branch within a few minutes of each other, the first pipeline will run and complete, but the next two will not. Ideally, the most recent pipeline would automatically resume once the first pipeline completes, ensuring that our most recent commit is tested properly.
I've tried using the REST API to start a new pipeline in the after-script section, but since the pipeline is still running, the new one gets paused again.
Is there any way to accomplish this behavior?
