heroku / heroku/heroku-buildpack-ruby
Save/restore yarn cache
Open
- Dominant language
- Ruby
- Stars
- 785
- Forks
- 1.8k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 8
Description
Every single one of our deploys is taking ~50s to install packages via yarn. This should be near-instantaneous when yarn.lock hasn't changed. It appears that the nodejs buildpack already takes care of saving/restoring the yarn cache.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing how the nodejs buildpack saves and restores the yarn cache, then locate the Ruby buildpack's package-install and deploy entry points. Done means yarn packages are restored when yarn.lock is unchanged, while changes to yarn.lock invalidate the cache; verify with the buildpack's available tests or a deploy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, ruby
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100