ci: evict majestic's moving S3 tarball from the dl cache too#2212
Merged
Conversation
The "Refresh moving-ref package downloads" step drops *-{HEAD,master,main,dist}.tar.gz
before each build so buildroot re-fetches the current ref. That matches the
majestic-webui dist (*-dist.tar.gz) but never matched majestic itself, which
downloads from S3 as majestic.<family>.<variant>.master.tar.bz2 (majestic.mk) —
a DOT separator, .tar.bz2, on the S3 host the old pattern spared as
"content-addressed". But that S3 object is a moving `master` build, re-uploaded
on every majestic CI run, with no .hash to force a refetch, so it froze in the
monthly output/dl cache while the webui refreshed. That desync shipped a
pre-x-groups majestic against the current webui, blanking the settings page
("No settings groups in schema").
Broaden the eviction to a regex covering both -ref and .ref separators across
gz/bz2/xz, so majestic.*.master.tar.bz2 and majestic-webui-dist.tar.gz are both
dropped while semver/SHA-pinned tarballs keep their cache. Mirrors OpenIPC/builder#109.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Mirrors OpenIPC/builder#109.
The "Refresh moving-ref package downloads" step evicts
*-{HEAD,master,main,dist}.tar.gzso buildroot re-fetches moving refs each run. That covers the webui dist (majestic-webui-dist.tar.gz) but not majestic, which downloads from S3 as:— dot separator,
.tar.bz2, on the S3 host the old pattern spared as "content-addressed". But that S3 object is a movingmasterbuild (re-uploaded each majestic CI run, no.hash), so it froze in the monthlyoutput/dlcache while the webui refreshed. That desync shipped a pre-x-groupsmajestic against the current webui → "No settings groups in schema." on the settings page.Broaden the eviction to a regex covering both
-ref/.refseparators across gz/bz2/xz:Evicts
majestic.*.master.tar.bz2andmajestic-webui-dist.tar.gzwhile sparing semver/SHA pins. The builder side (#109) is already merged and verified end-to-end: a republishedt31_lite_xiaomi-mjsxj03hl-nor.tgznow bundles a 2026-06-25 majestic with thex-groupsmanifest (was 2026-05-24).🤖 Generated with Claude Code