cancel outdated jobs on push #2

Closed
opened 2024-03-09 03:48:53 +00:00 by pennae · 3 comments
Owner

pushing an update to a CL should probably cancel jobs running for the now-outdated patchset. the result won't be useful for verification labels anyway and only binds up resources that are unlikely to lead to cached results for later (unless only the commit message changed, but us building mainly from flakes also renders that somewhat irrelevant?)

pushing an update to a CL should probably cancel jobs running for the now-outdated patchset. the result won't be useful for verification labels anyway and only binds up resources that are unlikely to lead to cached results for later (unless only the commit message changed, but us building mainly from flakes also renders that somewhat irrelevant?)
Owner

@pennae Is that still relevant? I feel like we have a canceller now (?)

@pennae Is that still relevant? I feel like we have a canceller now (?)
Author
Owner

oh yeah this has been done for a good while now, sorry

oh yeah this has been done for a good while now, sorry
Owner

no worries, thanks <3!

no worries, thanks <3!
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lix-project/buildbot-nix#2
No description provided.