test(e2e): single-environment scenario template + release.yaml coverage#64
Merged
Conversation
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.
Closes #26
Adds
e2e/scenarios/09-single-env-repo.yaml: a single-environment (environments: [prod]) multi-step scenario that exercises theReleaseGeneratorcode path. For single-env repos the CLI writes a release workflow (not a promote workflow) topromote.yaml, so this was the last generator path without any e2e coverage.The first orchestrate step includes a
workflow_filesassertion that verifies the generatedpromote.yamlcontains theUpdate Latest Release Stateretry loop (for attempt in 1 2 3 4 5,git fetch origin,git reset --hard,apply_release_state_edits), mirroring the pattern from08-state-push-retry.yamlfor the orchestrate path.The scenario then walks a two-commit trunk trunk model through orchestrate (draft RC at
prod) and a default promote (publishesv0.1.0), covering the orchestrate → promote lifecycle for a trunk-model single-env repo.