Repository navigation
Move the staging commit from tags to the revision annotation - #16
Merged
Merged
Conversation
This was referenced Oct 7, 2026
This was referenced Oct 9, 2026
alexadereyko
commented
Oct 9, 2026
An index is tagged run-<run id>-<run attempt> in place of <sha> and <short-sha>; the commit it was built from is its org.opencontainers.image.revision annotation. The fields a project adds to the staging metadata through opendaq-cmake-utils are published as annotations, and the com.opendaq.dependencies.* ones are repeated on the index. test-staging gives hello-module the revision of hello-core this way.
The windows-11-arm runner label moved to an image with Visual Studio 2026 only, and the Visual Studio 17 2022 generator finds no instance there. The job keeps the v143 toolset, which that image carries.
A package carries the revision and source of its build, so a package fetched by its digest says what it was built from.
A package carries the revisions of its dependencies from its metadata; the index no longer repeats them, and packages of one index that differ in them no longer fail the publish.
…index The script reads top to bottom: each artifact becomes an annotated manifest, the index carries their annotations and the dependency revisions they agree on, one copy publishes it.
The module package is given a second entry in CPACK_OPENDAQ_META_FIELDS, dependencies/test/revision, and the index and its packages are expected to carry it.
alexadereyko
force-pushed
the
jira/TBBAS-3549-staging-push-run-id-tags
branch
from
October 12, 2026 07:55
4d327b2 to
829c1c4
Compare
alien588
approved these changes
Oct 12, 2026
alien588
left a comment
alien588
left a comment
There was a problem hiding this comment.
LGTM, a small misc change requested (if needed). Approved otherwise
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.
Brief
Tag staging indexes by run instead of by commit, name the build on every package, and repeat the dependency revisions of the packages on the index.
Overview
staging-pushtags an indexrun-<run id>-<run attempt>in place of<sha>and<short-sha>.Every package carries
org.opencontainers.image.revisionandorg.opencontainers.image.source, as the index does. Thecom.opendaq.dependencies.*annotations of the packages are repeated on the index; a publish whose packages differ in them fails.test-staginggiveshello-moduletwo dependency revisions throughCPACK_OPENDAQ_META_FIELDS, requests its stagings by the run tag, and verifies the annotations of the published indexes and packages.The
windows-11-armjob ofreusablebuilds with theVisual Studio 18 2026generator: the runner image has no other Visual Studio.Caller migration
A request with
"tag": "<sha>"no longer resolves against an index published by this version; a caller requestslatestor the run tag.