Is it possible to automatically cancel the old builds that are waiting on the blocked step to avoid people accidentally unblocking old blocked builds? A use case could be someone unblocked an old blocked build that deploys an old version of the service to the production environment.
I know there is a “Skipping Builds” feature where we can cancel running intermediate builds but I want to cancel the build only during the cases when a newer execution of the pipeline is ahead of the older executions. This can happen when there are “block” steps in the pipeline.
Also, is there any other alternatives to achieve this?
Hi,
Is it possible to automatically cancel the old builds that are waiting on the blocked step to avoid people accidentally unblocking old blocked builds? A use case could be someone unblocked an old blocked build that deploys an old version of the service to the production environment.
I know there is a “Skipping Builds” feature where we can cancel running intermediate builds but I want to cancel the build only during the cases when a newer execution of the pipeline is ahead of the older executions. This can happen when there are “block” steps in the pipeline.
Also, is there any other alternatives to achieve this?