Repository navigation
feat(krater): pull CI's image instead of building on weft - #103
Merged
Merged
Conversation
Krater's CI now pushes ghcr.io/patchworklabsorg/krater:<sha> for each commit on main (krater#76). krater-build pulls it for the commit in source-rev, checks its org.patchworklabs.krater.rev label, and tags it <prefix>:<sha>; a failed pull or a wrong label falls back to today's build from source. Builds on weft starved the host twice on 2026-11-12 (staging and production both stopped answering for about 3 minutes). The unit runs at Nice 19 and idle I/O. Its definition changes, but restartIfChanged is off, so a switch restarts nothing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 13, 2026
jaspermayone
added a commit
that referenced
this pull request
Nov 13, 2026
* origin/main: feat(krater): blue/green portal deploys, on for staging (#104) feat(krater): pull CI's image instead of building on weft (#103) feat(ansible): run ad converge build from ad.yml (#105) feat(selvage): add a staging instance on twill (#102) feat(selvage): pass the admin web ui paths through nginx on twill (#100)
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
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.
Weft stops building Krater's image itself. This needs patchworklabsorg/krater#76, which pushes
ghcr.io/patchworklabsorg/krater:<full sha>for each commit on main.Why:
docker buildon weft starved the host twice on 2026-11-12 (18:03–18:06 and 19:22–19:25 UTC). Staging and production both stopped answering, even when only staging was deploying.What changes in
krater-build(both instances):<registry>:<sha>(new optionregistry, defaultghcr.io/patchworklabsorg/krater) with a 10-minute timeout.org.patchworklabs.krater.revlabel against the commit, then tags it<prefix>:<sha>and drops the registry tag, so the existing cleanup still works.Nice=19, idle I/O. The build itself runs inside dockerd, so this only covers git and the pull.restartIfChangedstays off, so the switch restarts nothing.Before it helps: the pull is anonymous, so the GHCR package must be public. I'll check after krater#76's first push; until then every pull just fails over to a build.
Tested:
nix build .#checks.x86_64-linux.krater-weftpasses, with new greps for the pull and label check.🤖 Generated with Claude Code