optimize CI matrix for PRs
Open
Nobody has claimed this yet.
area/testing
- Dominant language
- Go
- Stars
- 10.3k
- Forks
- 1.5k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 48
Description
A single Dockerfile test runs 26 times currently on PR CI.
4 workers (oci, containerd1.0, containerd, oci-rootless) * 2 modes (builtin, client) * 2 fileop modes
4 workers * gateway * 2 fileop modes
oci * gateway-experimental * 2 fileop modes
This is probably an overkill and we can leave the full matrix for master branch testing.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the PR CI configuration that defines the Dockerfile test matrix and compare the listed worker, gateway, mode, and file-operation combinations. Reduce redundant PR coverage while retaining the full matrix for master-branch testing, then verify the resulting CI jobs and coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dockerfile
- Domain
- ci-cd, testing-qa
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100