Skip to content

Resolve the openDAQ SDK staging by image revision and triplet - #29

Draft
alexadereyko wants to merge 3 commits into
mainfrom
jira/TBBAS-3553-stage-with-core-revision
Draft

alexadereyko wants to merge 3 commits into
mainfrom
jira/TBBAS-3553-stage-with-core-revision

Conversation

@alexadereyko

@alexadereyko alexadereyko commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Brief

Resolve the openDAQ SDK staging by its image revision and triplet instead of a tag.

Overview

  • stage.yml takes an opendaq-ref input; empty, the opendaq_ref file is used. The ref is resolved to a commit.
  • The openDAQ SDK staging is requested by org.opencontainers.image.revision and com.opendaq.package.triplet. One table in the resolve job maps each job to its triplet.
  • The module packages record that revision as com.opendaq.dependencies.opendaq.revision.
  • check-core-staging.yml asks for the staging by its revision.

The staging workflow takes an opendaq-ref input; empty, it uses the
opendaq_ref file. The ref is resolved to a commit, which the core
staging is found by and which the module records as
dependencies/opendaq/revision in its metadata. The core staging check
asks for the core by its revision.

The workflows take openDAQ-CI from jira/TBBAS-3547-staging-pull-by-annotations
and cmake-utils from jira/TBBAS-3548-staging-metadata-fields until the
reviews land and the v3 and v1.1.2 tags are set.
The output of the resolve job and the variable of the core staging
check take the name of the input and of the opendaq_ref file.
The resolve job lists each job with the triplet of the openDAQ staging
it builds against, and gives the jobs, the staging-pull requests and
the artifacts of the packages input from that table. A staging is asked
for by its triplet, which names the compiler and its version, and the
pulled artifacts are named opendaq-<triplet>.
@alexadereyko alexadereyko changed the title Publish stagings with the core revision Resolve the openDAQ SDK staging by image revision and triplet Oct 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant