Repository navigation
Add a skill for updating CI registry images - #408
Merged
Merged
Conversation
Refreshing a multi-arch CI image in the ci.trafficserver.apache.org:5000 registry was documented only in personal notes tied to one lab host. The process has several easy-to-miss steps: separate native amd64 and arm64 builds, a firewall window on the controller that every registry client needs, Podman's TLS defaults against the plain HTTP registry, and a manifest list assembled on docker1. This patch adds an update-ci-registry-image agent skill that walks through the full flow with the build hosts, controller, and manifest host as inputs rather than hard-coded names. It covers shipping the committed tree to a remote builder, pushing each architecture, publishing and verifying the manifest, and closing the registry port again afterward. Co-Authored-By: Claude Opus 5.5 Low <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
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.
Refreshing a multi-arch CI image in the ci.trafficserver.apache.org:5000
registry was documented only in personal notes tied to one lab host.
The process has several easy-to-miss steps: separate native amd64 and
arm64 builds, a firewall window on the controller that every registry
client needs, Podman's TLS defaults against the plain HTTP registry,
and a manifest list assembled on docker1.
This patch adds an update-ci-registry-image agent skill that walks
through the full flow with the build hosts, controller, and manifest
host as inputs rather than hard-coded names. It covers shipping the
committed tree to a remote builder, pushing each architecture,
publishing and verifying the manifest, and closing the registry port
again afterward.
🤖 Generated with Claude Code