-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Speedup the CI #3699
Speedup the CI #3699
Conversation
If the lock matches we can save the installation time entirely.
This will keep the cached bundle lean and swift.
42d5096
to
6971794
Compare
That's the suggested way of doing it in recent versions.
13a3003
to
6772329
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @elia! 🚤
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all seems sensible. There's a typo ("brach" instead of "branch") in one of the commit messages though if you wouldn't mind fixing that.
Invalidate all previous cache, starting from scratch will be faster than waiting for all caches to be replaced, which BTW doesn't happen if a key is already present.
15e3937
to
f822f54
Compare
@jarednorman I don't mind! 🙂 Thanks for pointing that out 👍 |
Description
The ci is taking longer and longer, with peaks of 6min just for restoring and saving the bundler's cache
Checklist: