Cache installed packages for future runs?
See original GitHub issueHi @eine! Do you know if there might be any way this action could cache packages that are installed with install
so that they don’t need to be re-installed each time a workflow runs? My setup-msys2
runs often take about 7 minutes to update and then install packages so it’d be nice to skip that. Looks like @actions/tool-cache
has the ability to cache directories:
https://github.com/actions/toolkit/tree/master/packages/tool-cache#cache
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (3 by maintainers)
Top Results From Across the Web
Caching APT packages in GitHub Actions workflow
Is there an elegant way to cache the installed system packages for future workflow runs? apt · github-actions · Share.
Read more >Understanding Cache, Install, and Install Cache - Jamf Nation
Cache : Saves the package to the Waiting Room folder for future installation. Install: Runs the package directly from the server
Read more >Caching Dependencies - CircleCI
Caching is particularly useful with package dependency managers such as Yarn, Bundler, or Pip. With dependencies restored from a cache, commands like yarn ......
Read more >Chapter 5 Testing with a reproducible environment
There's a third step that GitHub handles automatically — before the job is complete, the cache is created and our installed packages are...
Read more >bundle cache - Bundler
Copy all of the .gem files needed to run the application into the vendor/cache directory. In the future, when running [bundle install(1)][bundle-install], ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I was still sitting on
v0
so I wasn’t affected by the change. Just updated tov1
, with the newrelease
behavior alone you’ve shaved about 7 minutes off of my CI runs!By NOT using the default installation, update time was reduced from 7-12 min to 1-3 min:
I’m closing this issue, because
cache
is supported in v1.1.0. See https://github.com/eine/setup-msys2/blob/master/CHANGELOG.md#v110 and https://github.com/eine/setup-msys2#cache.@daviwil, using
update: true
will now use the custom installation. If you want to keep using the default installation in the environment (with the known caveats), setrelease: false
too.