[feature] Reusable E2E CI pipeline#21
Draft
NikolayDemchuk wants to merge 1 commit into
Draft
Conversation
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.
Signed-off-by: Nikolay Demchuk nikolay.demchuk@flant.com
Description
Add a reusable GitHub Actions workflow and
cmd/e2eCLI that run the same three-stage E2E pipeline (create-cluster→run-tests→teardown-cluster) through theClusterProviderSDK, with JUnit publishing and secret handling via temp files.Why do we need it, and what problem does it solve?
Module repos (starting with
sds-node-configurator) need a shared, low-overhead CI pattern for storage E2E without duplicating bash cluster setup and diverging from localmake e2e/ Ginkgo runs.What is the expected result?
Callers use
deckhouse/storage-e2e/.github/workflows/e2e-reusable.ymlwithsecrets: inherit; jobs provision the cluster via SDK, run tests with optional--label-filter, upload JUnit to PR Checks, and always tear down the cluster in the final job.Checklist