[oncall toil] Use inrepoconfig for prow jobs in all repos
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 83
- Forks
- 160
- PR merge metrics
- No merged PRs in 30d
Description
Inrepoconfig(https://github.com/kubernetes/test-infra/blob/master/prow/inrepoconfig.md) allows each repo setting up prow jobs in its own repo instead of everything in test-infra, the benefits:
- Promotes self-service
- Presubmit flows get validated in PRs before applying
To make sure there is no regression doing this, it might be required to refactor prow job config generator so that it still serves each repo as it is today
/kind enhancement
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 by reading prow/inrepoconfig.md and tracing the existing prow job config generator. Compare how jobs are currently served for each repository, then determine the changes needed to support in-repository configuration without regressions. Done means all repositories continue receiving the expected prow jobs while using inrepoconfig.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100