speed up CI
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
CI is taking a long time to run our builds. We should
1. split up our builds. There's no need to run `go test` and `go test -race` sequentially. These can be separate jobs.
2. use self-hosted runners running on beefier hardware, and without the concurrency restrictions that GitHub Actions imposes
Contributor guide
No contributing guide indexed for this repository
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 repository's GitHub Actions build configuration and the current `go test` and `go test -race` jobs. Determine how to run those jobs independently and how self-hosted runners would remove the stated concurrency restrictions; done means CI builds complete faster with both changes addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100