You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f92b7c3
Browse filesBrowse the repository at this point in the historyBrowse files
Run full CI on release branches on a schedule instead of every push (#75420)
* Run full CI on release branches on a schedule instead of every push
While a release is prepared, backports land on vX-Y-test in bursts and
every push started a full AMD and ARM run. In the week of 15-21 October
v3-4-test triggered 177 such runs; 133 of them were cancelled by the
next push after already using hundreds of runner-minutes each, which
made release-branch pushes one of the largest single consumers of the
ASF's shared runners. Each backport PR has already run CI against the
branch, so the branch needs a full run of its current HEAD a few times
a day rather than one per merged commit.
Release managers still need quick feedback on a broken backport, so a
push still runs the tests for what changed since the last successful
run of the branch. Testing from the last success rather than from the
pushed commit alone means changes whose runs failed or were cancelled
by a newer push are not left untested.
Scheduled canaries that have nothing new to test - no commit since the
last successful full run - only repeat that run, so they now finish
without building anything.
Generated-by: Claude Opus 5
* Address review: fail open, keep docs publishing on main, check full push range
- check-run-needed lookups fail open (push: all tests, canary: runs), and
notify-slack posts unless the canary was a no-op.
- Docs publishing steps of a canary run only on main: release branches build
a subset of the docs, which `aws s3 sync --delete` would publish over the
docs bucket. release-branch-ci.yml skips branches this is not backported to.
- Basic static checks of a push cover the files changed since the last
tested commit, as its test selection does.
- List pushed changes with --no-renames, as diff-tree does.
- A dispatched full run upgrades to newer dependencies, as a scheduled one.
Generated-by: Claude Opus 5
0 commit comments