Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache node and Yarn installation #7

Open
jonas opened this issue Jun 26, 2017 · 4 comments
Open

Cache node and Yarn installation #7

jonas opened this issue Jun 26, 2017 · 4 comments

Comments

@jonas
Copy link
Collaborator

jonas commented Jun 26, 2017

From https://github.com/olafurpg/metadoc/pull/4#issuecomment-310866379:
It seems npm and yarn is installed on every ci run and node_modules is not cached. It would be nice to cache those too, but I don't know what's the best way to achieve that. The yarn.lock and node_modules are located in nested directories.

@olafurpg
Copy link
Member

We could embed an sbt-launcher.jar in the repo and configure .travis.yml to be a js project. It should be possible to cache the nested node_modules directories, just by hard-coding them.

@gabro
Copy link
Member

gabro commented Jun 27, 2017

Just throwing there a random idea, but due to the cross-breed nature of the project it would probably be easier to use Drone instead of Travis, crafting a custom Docker image with both scala and js.

However that would require hosting an installation of drone, but there may be one in place already for the Scalacenter, right @olafurpg?

@olafurpg
Copy link
Member

I prefer to use Travis because it's a lot simpler to setup caching. I was the one pushing for Drone at the SC originally, but at this point I've spent so much time on it that I prefer Travis.

@olafurpg
Copy link
Member

After #101 the npm download size is significantly smaller, CI went from 10 minutes to 5 minutes. Would still be nice to cache node_modules.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants