Open purplecabbage opened 5 years ago
Good point.
Also I noticed that the main time consuming command on windows build isnpm install
. It's very slow on windows. If the main concern is travis build time (not size), then we should also check if there are techniques around to optimize npm install
.
We should use npm ci
if we have a lock file. https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable
We should check if this speeds up the process. https://docs.travis-ci.com/user/caching/#npm-cache If it works, we also need to check how long the cache would stay before being invalidated.
Currently every commit/pr triggers an end to end build, which includes installing google chrome. It's 54MB and our tests on windows are taking 8-10 minutes.