search

krlmlr / r-appveyor

Tools for using R with AppVeyor (https://appveyor.com)
132 stars 60 forks source link

Take advantage of build caching #31

Closed jimhester closed 8 years ago

jimhester commented 9 years ago

Appveyor supports caching of build dependencies (http://www.appveyor.com/docs/build-cache).

For CRAN dependencies they could then be selectively updated with update.packages(), which would then invalidate and update the cache.

Github dependencies would need some other form of updating, I guess, as drat use is not widespread.

krlmlr commented 9 years ago

Caching seems to require a copy from/to Azure storage, both before and after building. This slows down the build and diminishes potential benefits. Installing a binary package on Windows is fast, and I don't have much hope that caching will further improve this. It's different for source packages, but r-appveyor could help providing binary builds via drat (#29), making source installs unnecessary.

Do you have experience with AppVeyor caching?

jimhester commented 9 years ago

I do not have experience with it and that is true about binary builds on windows, I'll close this.

krlmlr commented 8 years ago

Important for testing R 3.4.0.

krlmlr commented 8 years ago

Should be added to the devtools template, too.

mlt commented 8 years ago

It would be nice to cache R & RTools installers to avoid re-downloading again and again.

krlmlr commented 8 years ago

The cache is limited to 100 MB, can't cache R or Rtools. (Download + install of R takes just under 30 seconds now, I guess we'll have to live with that.)

mlt commented 8 years ago

It is 100 MB per cache entry IIRC. While it is a bummer with RTools (103Mb as I just checked for 3.4.x), R exes should be cacheable (~70MB).