[Feature Request] Basic build caching on CI
- Dominant language
- Objective-C
- Stars
- 469
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
CircleCI has some cache support that should let us cache the artifacts to some extent. It's pretty easy to add in, but it depends on the flow you want to use:
1. Cache artifacts on the master branch always with a key
or
2. Use the master cache, then cache artifacts on each branch after a PR is made and built under a separate key
As long as CircleCI is running tests on the "default" branch each time 1 isn't too bad alone and should give most of the benefits
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the repository's CircleCI configuration and reviewing how the default branch builds artifacts. Decide whether to use a master-branch cache or separate branch caches, then verify that repeated builds restore and update the intended artifact cache while tests still run successfully.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100