Feature: force through by cancelling previous
Opened this issue · 2 comments
eddiewebb commented
I could see where this would be ideal in hung situations, but could also . have cascading effect if ill timed.
chrismo commented
eddiewebb commented
Great question. The key distinctions over 'auto cancel redundant workflows
' would be:
- can be applied to specific jobs instead of entire workflow
- allows the various parameters of branches, tag, or job names to consider
- still waits configured delay before calling the cancel of previous
workflows.
That said, I think the reason most people avoid the setting you shared
would also be an issue with this feature. Cancelling the jobs already
underway could leave assets in an invalid interim state causing downtime or
manual intervention.
…On Wed, Apr 10, 2024, 6:42 PM chrismo ***@***.***> wrote:
Would this essentially be implementing this feature but on the default
branch?
image.png (view on web)
<https://github.com/eddiewebb/circleci-queue/assets/8092/c83557a8-d982-4a8b-bb72-0cdd6bb85841>
—
Reply to this email directly, view it on GitHub
<#47 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABIEWSTJ3PICXLNANWBZ2ODY4W55VAVCNFSM4J6IKGI2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBUHA2TKMZVHE4A>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>