ci(fleet): add the monorepo example repo to the fleet roster - #532
Merged
Merged
Conversation
joshua-temple
force-pushed
the
feat/fleet-monorepo-roster
branch
2 times, most recently
from
July 8, 2026 15:51
92bc7bc to
0110f0c
Compare
Add the cascade-example-monorepo repository to both fleet rosters (the fleet-e2e fan-out list and the suite repin list) so the whole-fleet-green run validates the per-component monorepo behavior on the release-candidate binary alongside the single-component repos. It joins the light remainder lane. Refs #289, #299. Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
joshua-temple
force-pushed
the
feat/fleet-monorepo-roster
branch
from
July 8, 2026 15:57
0110f0c to
8150df2
Compare
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.
What
Add the new
cascade-example-monoreporepository to both fleet rosters so the whole-fleet-green run validates the per-component monorepo behavior on the release-candidate binary alongside the single-component repos..github/workflows/fleet-e2e.yaml: addmonorepoto theREMAINDERlane (a light standalone example, like3env)..github/workflows/suite-rc-repin.yaml: addmonorepotoREPOSso the just-in-time repin regenerates its per-component workflows on the rc binary.The repository (
stablekernel/cascade-example-monorepo) is created and populated with a two-component (api, web), three-environment example whose suite proves independent per-component advancement. It needs itsCASCADE_STATE_TOKENsecret set before the first fleet run.Verification
Both rosters stay in sync (the two-place roster is the known drift risk). actionlint clean; the change is a static roster-name addition with no dynamic input.
Refs #289, #299.