oasisprotocol / oasisprotocol/cli
ci: Speed up ci-tests workflow
Open
Nobody has claimed this yet.
ci
tests
- Dominant language
- Go
- Stars
- 80
- Forks
- 23
- Avg merge
- 9h 43m
- Merged PRs (30d)
- 3
Description
At the time of writing, the Build code and Run tests steps take in the order of 45-60 seconds:
Figure out if we could speed this up.
Some ideas:
- Caching to speed up building (most unchanged) Go code.
- Re-using built Go code for tests. Do tests compile all the Go code again?
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 with the ci-tests workflow and inspect its Build code and Run tests steps, measuring their current 45–60 second durations. Investigate whether Go build caching or reusing compiled code can reduce the time, and consider the work done when the workflow is measurably faster without losing test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100