Setup the cache server #1482
Merged
Setup the cache server #1482
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NullVoxPopuli
force-pushed
the
use-cache-server
branch
3 times, most recently
from
6bbedae to
aefe74a
Compare
NullVoxPopuli
force-pushed
the
use-cache-server
branch
from
af1757f to
dfa3d1e
Compare
|
it's not yet perfect, but its an improvement. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because we now build each package 3 times (prod (ESM), dev (ESM), and (CJS)), and because building is required before linting, the
lintjob takes a while.By using the cache server, we can hopefully speed up parts of CI.
For example, previously, in: #1481 -- https://github.com/glimmerjs/glimmer-vm/actions/runs/6721577834/usage
With this PRs changes, we see: https://github.com/glimmerjs/glimmer-vm/actions/runs/6726246999/usage