Skip to content

[ci] Test release flow in CI - #35

Open
pamaury wants to merge 2 commits into
mainfrom
ci_release
Open

pamaury wants to merge 2 commits into
mainfrom
ci_release

Conversation

@pamaury

@pamaury pamaury commented Nov 16, 2026 •

Copy link
Copy Markdown
Collaborator

This PR creates a CI flow which automatically test the pre-sign/post-sign release flow. The setup is a bit involved so I am trying to explain how it works below. This PR should also be reviewed with the content of ot-sku-testing repository: https://github.com/lowRISC/ot-sku-testing

  1. The user creates a PR (or push to branch on the lowRISC/ot-sku repo)
  2. The .github/workflows/test-release-ci.yml flow runs and uses the cross-ci mechanism to trigger a https://github.com/lowRISC/ot-sku-testing/blob/main/.github/workflows/trigger-test-release.yml in the ot-sku-testing repository. This repository is technically a fork of ot-sku (for reasons noted below) but it is actually just a skeleton repo with the minimal yaml files to support the testing working.
  3. The trigger-test-release.yml in the ot-sku-testing now runs. The takes the SHA of the requested PR/branch and replicates it on ot-sku-testing. Since ot-sku-testing is a fork of ot-sku, they share the same underlying git storage so an ot-sku SHA is also a valid ot-sku-testing SHA!
  4. It then trigger test-release.yml coming from the PR/branch but runs it **on the ot-sku-testing repository.
  5. The test-release.yml finally exercices the release flow. Since it runs in another repository, it can freely creates branch and releases. In the details, it:
    • does a bunch setup
    • runs the pre-sign flow and creates a branch
    • checks out the pre-sign branch and runs a offline sign of the pre-sign artifacts
    • pushes the signature to the pre-sign branch
    • runs the post-sign flow from the pre-sign branch

Example:

Final remarks: this works because currently the ot00 sku is signed with fake keys. When we change it to real keys, we obviously won't be able to sign in CI. The proposal would be to have a bazel setting so that we can swicth ot-sku to fake keys for testing purposes.

Signed-off-by: Amaury Pouly <amaury.pouly@opentitan.org>
Signed-off-by: Amaury Pouly <amaury.pouly@opentitan.org>
Comment on lines +127 to +134
- name: Download OpenTitan devbundle
env:
DEVBUNDLE_RELEASE: devbundle-2026-10-21-1
run: |
set -e
gh release download -R lowRISC/opentitan "$DEVBUNDLE_RELEASE" -O devbundle.tar.xz
mkdir devbundle
tar -xf devbundle.tar.xz -C devbundle

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we migrate this to opentitan-signing-infra at some point?

@AlexJones0 AlexJones0 Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but I think that's gated on using opentitan-signing-infra on earlgrey_1.0.0, which is in turn ideally gated on me merging back all of my SLH-DSA implementation and fixes, for which I am trying to backport to master at the same time so I can update things in sync and get parity across the branches. Unfortunately I have been running into a sequence of large PRs that I needed to backport to master first, but I am hoping I am mostly through that now and can focus on the backports, so we can resolve this situation.

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.

3 participants