ci: repin example fleet to the rc under test before fan-out#217
Merged
Conversation
The fleet gate logged the resolved rc as the version under test, but the suites installed whatever each repo's manifest was statically pinned to, so a fresh rc was never actually validated until a manual repin. Add a repin job that downloads the rc binary, sets each example repo's manifest cli_version to the rc, replaces any other in-repo rc refs, regenerates the workflows against the rc, and pushes the result to each repo's main (idempotent, [skip ci], force-with-lease). All suite jobs now gate on repin so none run against a stale pin. Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
joshua-temple
force-pushed
the
ci/fleet-auto-repin
branch
from
dd0956e to
fd142a9
Compare
auto-merge was automatically disabled
June 18, 2026 03:47
Pull request was closed
Signed-off-by: Joshua Temple <joshua.temple@stablekernel.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
1 participant
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.
Problem
The Fleet E2E gate resolves the rc version and logs it as "version under test", but the dispatch-suite action passes no version, so each example suite installs whatever its manifest is statically pinned to. A fresh rc was therefore never validated by the fleet until someone manually repinned the repos - the label outran reality.
Fix
Add a
repinjob (needs: resolve) that runs before all suite jobs. It downloads the rc linux/amd64 binary, verifiescascade versionmatches the rc, then for each of the 8cascade-example-*repos: clones main with the state token, sets the manifestcli_versionto the rc, replaces any other in-repo rc-version refs, regenerates the workflows with the rc binary, and commits + pushes only if something changed (idempotent, DCO-signed via --no-gpg-sign since CI has no GPG key,[skip ci], force-with-lease).primaryandindependentsnowneeds: [resolve, repin](dependents inherits via primary), so no suite runs against a stale pin. Cloning fresh main + version-sed + regen preserves every hand-written suite feature; only generated workflows are rewritten. The gate summary now reflects the version actually pinned.Verification