-
Sub-task
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
None
-
False
-
False
-
ToDo
-
0
-
0
-
Untriaged
From various comments in team meetings it appears as though many experienced engineers do not know where to look for test results and debugging information in the log archives from prow. Perhaps we can improve the usability
- Openshift CI: Debug Guide
https://docs.google.com/document/d/1zGQLXZMWlRXV19t28VEb51fSs6scRbeK9s14K5a9Bt8/edit?authuser=1
- Exposing custom items to ${ARTIFACT_DIR} https://docs.ci.openshift.org/docs/architecture/step-registry/#exposing-artifacts
- TestGrid https://docs.ci.openshift.org/docs/how-tos/add-jobs-to-testgrid/#adding-a-non-release-gating-job-to-testgrid
- ( Hiteshwari already added slack alerts ) https://docs.ci.openshift.org/docs/how-tos/notification/
Use Case: copy velero logs to after each test invocation
https://github.com/openshift/oadp-operator/blob/master/tests/e2e/install_suite_test.go#L41