Provide container logs in CI as an artifact
- Dominant language
- Shell
- Stars
- 26
- Forks
- 70
- PR merge metrics
- No merged PRs in 30d
Description
Similar as we dump the cluster state with all resources in all namespaces in [`dump_cluster_state`](https://github.com/knative/hack/blob/ab9b69024c39e5f5a8d98034d5db6284278d60cf/infra-library.sh#L37) ([`fail_test`](https://github.com/knative/hack/blob/ab9b69024c39e5f5a8d98034d5db6284278d60cf/e2e-tests.sh#L118)), it would be good to have all the pod/container logs too (e.g. in a tar ball) and provided as an artifact in prow.
This would help on debugging CI issues
Contributor guide
Research direction
Start with dump_cluster_state in infra-library.sh and fail_test in e2e-tests.sh to understand how CI failure data is collected. Trace how Prow artifacts are exposed, then define the container and pod logs to package and verify that the tarball is available as a CI artifact after failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100