chore(ci): add skeleton for nightly E2E matrix workflow #1680
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
yachmenevas
requested review from
nevermarine and
universal-itengineer
as code owners
yachmenevas
force-pushed
the
chore/ci/e2e-matrix-skeleton
branch
from
7f76051 to
20821ac
Compare
…atrix setup and cleanup - Setup profiles: single profile 'sds' with storage class 'sds-replicated-volume' - Matrix setup (prepare): real setup logic with tools installation, kubeconfig, values preparation - Cleanup: real cleanup logic for nightly-nested-e2e-* namespaces Signed-off-by: Anton T. <[email protected]>
yachmenevas
force-pushed
the
chore/ci/e2e-matrix-skeleton
branch
from
8570e30 to
744dba8
Compare
Contributor
Author
|
Closing PR - reverting to skeleton state |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Add a minimal skeleton for the nightly E2E matrix workflow.
Preserves triggers, job order, and profile matrix; replaces logic with echo placeholders only.
Why do we need it, and what problem does it solve?
Validate triggers, dependencies, and matrix expansion without side effects before introducing real setup/tests/notifications.
What is the expected result?
Workflow runs on schedule/dispatch/PR, expands profiles matrix, and prints stage/profile messages only.
Checklist
Changelog entries