Refresh the image cache on canary pushes, not only on the schedule - #71137
Merged
Conversation
Release branches are built by push only, and their cache refresh sat behind the whole test matrix. A red branch never refreshed its cache at all, and the staler it got the slower it was to turn green -- v3-3-test went eight days without a refresh while its runs kept failing.
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496 and
jscheffl
as code owners
August 5, 2026 03:38
boring-cyborg
Bot
added
area:dev-tools
backport-to-v3-3-test
vatsrahul1001
approved these changes
Aug 5, 2026
Contributor
Backport successfully created: v3-3-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
potiuk
added a commit
that referenced
this pull request
Aug 5, 2026
… schedule (#71137) (#71138) Release branches are built by push only, and their cache refresh sat behind the whole test matrix. A red branch never refreshed its cache at all, and the staler it got the slower it was to turn green -- v3-3-test went eight days without a refresh while its runs kept failing. (cherry picked from commit 64dd235) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Aug 5, 2026
… schedule (#71137) (#71138) Release branches are built by push only, and their cache refresh sat behind the whole test matrix. A red branch never refreshed its cache at all, and the staler it got the slower it was to turn green -- v3-3-test went eight days without a refresh while its runs kept failing. (cherry picked from commit 64dd235) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
dabla
pushed a commit
to dabla/airflow
that referenced
this pull request
Aug 14, 2026
…pache#71137) Release branches are built by push only, and their cache refresh sat behind the whole test matrix. A red branch never refreshed its cache at all, and the staler it got the slower it was to turn green -- v3-3-test went eight days without a refresh while its runs kept failing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The early cache push was gated to
scheduleandworkflow_dispatch, so it never ran for a merge into a release branch. Those branches are built bypushonly, and their other refresh path — the Regular cache push infinalize-tests.yml— sits behind the whole test matrix. A branch whose CI is failing therefore never refreshes its image cache at all, and the staler the cache gets the slower every build on it becomes, which makes it harder to get green again.v3-3-testhas been in exactly that state: its last successful canary push run was 2026-07-28, so its registry cache is eight days old, and every build against it — including release-constraints runs — pays for it.mainis unaffected either way. It is not built on push, so it keeps refreshing through the scheduled canary.Pull requests stay excluded.
canary-runis also true for a PR carrying thecanarylabel, and pushing cache from an unmerged branch is not something a label should authorise — so the condition matches the one the Regular cache push already uses.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Opus 5 (1M context) following the guidelines