-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Toggle audit #340
Toggle audit #340
Conversation
Note As this is a draft PR no triggers from the PR body will be handled. If you'd like to trigger them while draft please add them as a PR comment. |
There were differences in the rendered Helm template, please check! Output
|
/run cluster-test-suites |
Oh No! 😱 At least one test suite has failed during the Be sure to check the full results in Tekton Dashboard to see which test suite has failed and then run the following on the associated MC to list all leftover resources: PIPELINE_RUN="pr-cluster-azure-340-cluster-test-suiteslld4b"
NAMES="$(kubectl api-resources --verbs list -o name | tr '\n' ,)"
kubectl get "${NAMES:0:${#NAMES}-1}" --show-kind --ignore-not-found -l cicd.giantswarm.io/pipelinerun=${PIPELINE_RUN} -A 2>/dev/null |
cluster-test-suites
📋 View full results in Tekton Dashboard Rerun trigger: Tip To only re-run the failed test suites you can provide a |
CAPZ Private is currently expected to fail, see https://gigantic.slack.com/archives/C04TGHDEF/p1725548655300869 |
Towards: giantswarm/roadmap#3669
Checklist
Trigger E2E tests
/run cluster-test-suites