Cancel redundant workflow jobs if a new one comes in

If a workflow gets triggered multiple times, for example, multiple commits being pushed in rapid succession to a specific branch, it will create multiple jobs and queue them up. This ends up resulting in multiple builds, deployments etc all in a row when really the desire is to just have the most recent one go out.

I think pending jobs should be canceled or disregarded in the event of a new job.

4 Likes

Agreed.
That feature would save computing resources of build servers.

We could refer similar features of CI services.

https://circleci.com/docs/2.0/skip-build/#auto-cancelling-a-redundant-build