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

chore: cache node_modules #2595

Merged
merged 6 commits into from May 14, 2018

Conversation

Projects
None yet
3 participants
@DanielRuf
Contributor

DanielRuf commented May 4, 2018

No description provided.

@kibertoad

This comment has been minimized.

Collaborator

kibertoad commented May 4, 2018

What are the benefits of this?

@DanielRuf

This comment has been minimized.

Contributor

DanielRuf commented May 4, 2018

It caches the node_modules and is partly an alternative to npm ci. If there is a cache with the same deps it will load the cache instead of installing all deps again = faster builds.

DanielRuf added some commits May 4, 2018

@DanielRuf DanielRuf changed the title from chore: use yarn cache to chore: cache node_modules May 4, 2018

@kibertoad

This comment has been minimized.

Collaborator

kibertoad commented May 4, 2018

Hell yeah, difference seems to be quite noticeable.

@DanielRuf

This comment has been minimized.

Contributor

DanielRuf commented May 4, 2018

Can be probably better in combination with the other PRs and with following builds / PRs.

Unfortunately the env is not the best for all cases https://docs.travis-ci.com/user/reference/overview/#Virtualisation-Environment-vs-Operating-System

@elhigu

This comment has been minimized.

Collaborator

elhigu commented May 14, 2018

This seems like a good idea 👍 I have experienced issues with CI npm caches earlier (not updating to new versions to libs properly etc.), but I think we can give this a shot to see if there are any drawbacks this time (I have never used travis cache).

@elhigu elhigu merged commit e3beaf2 into tgriesser:master May 14, 2018

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
@elhigu

This comment has been minimized.

Collaborator

elhigu commented May 14, 2018

thanks!

@DanielRuf

This comment has been minimized.

Contributor

DanielRuf commented May 14, 2018

This seems like a good idea 👍 I have experienced issues with CI npm caches earlier (not updating to new versions to libs properly etc.), but I think we can give this a shot to see if there are any drawbacks this time (I have never used travis cache).

If this cache strategy creates any problems we can also try $HOME/.npm as alternative. So fr I saw no issues with the current cache strategy.

@DanielRuf DanielRuf deleted the DanielRuf:chore/use-yarn-cache branch May 14, 2018

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