[zeek/spicy] 76b83f: Automatically cancel exisiting GH CI workflows on ...

[Benjamin Bannier]

Branch: refs/heads/topic/bbannier/gh-ci-concurrency
Home: https://github.com/zeek/spicy
Commit: 76b83f5802fd0378e4a5592b7ed6968c3151a64b
https://github.com/zeek/spicy/commit/76b83f5802fd0378e4a5592b7ed6968c3151a64b
Author: Benjamin Bannier <benjamin...@corelight.com>
Date: 2026-06-03 (Wed, 03 Jun 2026)

Changed paths:
M .github/workflows/benchmark.yml
M .github/workflows/check.yml

Log Message:
-----------
Automatically cancel exisiting GH CI workflows on PR update

Previously we would run all GH actions CI workflows to completion, even
if the PR was updated and another run was started. Since we only have a
limited number of workers available this causes contention across the
whole GH org. It is also inconsistent with how Cirrus CI behaved, so
people are not at all concious about cancelling outdated jobs.

This PR changes the configuration of all workflows which trigger for
pull requests to automatically cancel existing jobs on updates,
mirroring the behavior of Cirrus CI.



To unsubscribe from these emails, change your notification settings at https://github.com/zeek/spicy/settings/notifications

[Benjamin Bannier]

Branch: refs/heads/main

Home: https://github.com/zeek/spicy
Commit: 76b83f5802fd0378e4a5592b7ed6968c3151a64b
https://github.com/zeek/spicy/commit/76b83f5802fd0378e4a5592b7ed6968c3151a64b
Author: Benjamin Bannier <benjamin...@corelight.com>
Date: 2026-06-03 (Wed, 03 Jun 2026)

Changed paths:
M .github/workflows/benchmark.yml
M .github/workflows/check.yml

Log Message:
-----------
Automatically cancel exisiting GH CI workflows on PR update

Previously we would run all GH actions CI workflows to completion, even
if the PR was updated and another run was started. Since we only have a
limited number of workers available this causes contention across the
whole GH org. It is also inconsistent with how Cirrus CI behaved, so
people are not at all concious about cancelling outdated jobs.

This PR changes the configuration of all workflows which trigger for
pull requests to automatically cancel existing jobs on updates,
mirroring the behavior of Cirrus CI.

Commit: 9be24aa951e8d41569b4a03ab7e4568b0fa0bf31
https://github.com/zeek/spicy/commit/9be24aa951e8d41569b4a03ab7e4568b0fa0bf31

Author: Benjamin Bannier <benjamin...@corelight.com>
Date: 2026-06-03 (Wed, 03 Jun 2026)

Changed paths:

M .github/workflows/check.yml

Log Message:
-----------
Do not run concurrent GH actions workflow for anything but tags [skip ci]

While Cirrus CI only cancelled concurrent jobs for the same PR, this
goes a step further and cancels existing jobs for anything but tag
builds. For `master` this reflects our workflow of pushing individual
merges in rapid succession where we only care about the last push. This
should free up additional resources so jobs can schedule faster.


Commit: 8de3833a1ed94b99a668cc4972a867264a987b35
https://github.com/zeek/spicy/commit/8de3833a1ed94b99a668cc4972a867264a987b35

Author: Benjamin Bannier <benjamin...@corelight.com>
Date: 2026-06-03 (Wed, 03 Jun 2026)

Changed paths:
M .github/workflows/benchmark.yml
M .github/workflows/check.yml

M CHANGES
M VERSION

Log Message:
-----------
Merge branch 'topic/bbannier/gh-ci-concurrency' [skip ci]


Compare: https://github.com/zeek/spicy/compare/35b0dc9279b1...8de3833a1ed9