Consider mozilla/sccache instead of Swatinem/rust-cache
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.6k
- Forks
- 1.3k
- Avg merge
- 8h 47m
- Merged PRs (30d)
- 19
Description
With the majority of build jobs moving to self-hosted runners, it might be a good idea to consider using sccache on S3 instead of Swatinem/rust-cache.
The sccache can grow quite quickly which makes it less than ideal candidate as a default cache for hosted GHA runners. With self-hosted the cache size should less of an issue so it might provide further speed-ups.
As a fallback, sccache can be also configured to work with hosted GHA runners.
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
Review the linked sccache S3 and GHA documentation, then inspect this repository's GitHub Actions build jobs and current Swatinem/rust-cache configuration. Done means reaching a decision on the cache approach and defining the required configuration for self-hosted and hosted runners.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- build-system, ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100