How do I cache brew install node?

[kitsunde]

It installs to /usr/local/Cellar/node but what other stuff does brew setup when it links?

[levlaz]

Please take a look at this doc regarding how cache works.

You cannot cache anything outside of your home directory so you will need to install this into your home folder if you want to keep it around in the cache.

Please note, that we do not officially support caching node like this on OS X containers. This is because unlike the Linux containers that run on AWS and have very quick access to S3, the cache is pulled down from S3 to the Mac Containers that run in a separate Data Center. Depending on the network that day this may be slower or faster than installing it via homebrew,

[GeoffreyPlitt]

@levlaz I haven’t seen any documentation saying that you can only cache home folder. Here’s an example in Circle’s docs that shows the opposite is true:

Installing android build tools 23.0.2

this adds roughly 21 seconds to the build not 1-2 mins… or even 4 like some people are saying… if you are redownloading the build tools each build you DO NOT have circleci configured properly. the dependencies are supposed to be cached. My build runs a step called restore cache for 17 seconds, but after that 17 seconds the same script that usually takes over 1 minute to download dependencies just does a filesystem check that the cache has not been invalidated and is present and continues on, t…

Please advise, thanks.

[levlaz]

Sorry for the confusion. You can only cache things that are owned by the circleci user (ubuntu on Linux and distiller on OS X).

Its simpler to work in the home directory since processes begin to break when you try to chown random things.