Add staging-pull and pull the core through ghcr in the test - #8
Open
alexadereyko wants to merge 2 commits into
Open
Add staging-pull and pull the core through ghcr in the test#8alexadereyko wants to merge 2 commits into
alexadereyko wants to merge 2 commits into
Conversation
alexadereyko
force-pushed
the
jira/TBBAS-3295-staging-pull
branch
from
July 20, 2026 14:40
828cfd0 to
0fe81ba
Compare
alexadereyko
force-pushed
the
jira/TBBAS-3295-staging-pull
branch
2 times, most recently
from
July 21, 2026 14:05
3252c7c to
0eed434
Compare
alexadereyko
force-pushed
the
jira/TBBAS-3292-staging-push
branch
from
July 22, 2026 12:48
bf3412e to
e483851
Compare
staging-pull fetches a package's manifest and resolves its children by descriptor annotations, globs included, then pulls the matches as tarballs into a deps artifact. A file-name collision between two pulled artifacts is an error.
alexadereyko
force-pushed
the
jira/TBBAS-3295-staging-pull
branch
from
July 22, 2026 13:02
0eed434 to
aa642e2
Compare
JakaMohorko
approved these changes
Jul 23, 2026
Public packages pull anonymously and a fork PR only has a read-only token, so warn and continue instead of failing the pull when login does not succeed. run() gains a fatal flag; fetch and pull stay fatal.
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.
Depends on:
Brief
Add
staging-pull, a reusable workflow that resolves requested staging packages in an OCI registry (ghcr) to digests, pulls them as tarballs, and uploads them as an artifact.Description
The input is a list of artifacts to produce, each with this structure:
artifact— the name of the artifact to upload.packages— the packages the artifact is assembled from; each is resolved against its index and every matching child is pulled into it.path/tag— the package path (its OCI index) and the tag that picks a specific index.annotations— how the child is resolved. In the general case a child is picked by itsorg.opencontainers.image.title(the file name). All values are globs, so you match on exactly the fields you care about — pin the compiler where it's deterministic, leave it open where the runner owns it (*-macos-apple-clang-*). For a more precise resolve, usecom.opendaq.*annotations (present when the staging carried astaging-meta.json).The workflow fetches the index at
path:tagand matches each child's descriptor annotations against the globs in a single request — no per-child manifest fetch. A request with no match is "not found" and fails; every match is pulled by digest — more than one is fine — but two pulled artifacts may not share a file name, since they'd clobber each other in the artifact, which fails loudly. The pulled tarballs and amanifest.json(what was resolved: path, tag, digest, title, annotations) go into the artifact, so the build can pin by digest. One matrix job per entry uploads one artifact.