CI enhancement tasks
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
There are some tasks to enhancement on CI
-
Do not use ubuntu
latestor MacOSlatestrunners, please set the special versions in GitHub workflows, them are not good at reproducibility on timeline. Ref: https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources
-
Update the base images that we used in
Dockerfilefiles. -
Think about whether and how to implement the heavy test jobs.
-
Add the prow
OWNERSfiles to enable the standard reviewing/approval flow. -
Add the repo into the controlling list of ti-chi-bot same as
tiflowrepo. -
Guard for config/API scopes with prow code owner mechanism.
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 reviewing the GitHub workflow files and the Dockerfile files referenced in the checklist, then inspect the repository's existing prow configuration and OWNERS files. Separate the unchecked tasks into concrete changes, including base-image updates, heavy test jobs, and prow code-owner scope guards. Done means each selected task has an implemented configuration change and passing CI or an agreed design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, dockerfile, github-actions, go
- Domain
- build-system, ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100