Cache npx-downloaded jscpd in CI integration test#24
Merged
Conversation
The integration test runs `npx jscpd@<version>` for real, which downloads and installs the ~22 MB jscpd tree into the npx cache on every cold runner (~9s vs ~1s warm). setup-node's npm cache is keyed on package-lock.json, which never changes for jscpd, so it can't keep this warm. Add a dedicated actions/cache step that persists the npx cache directory, keyed on OS, node version, and the jscpd DEFAULT_VERSION from src/lib.js. Bumping the version naturally invalidates the cache.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The integration test runs
npx jscpd@<version>for real, which downloadsand installs the ~22 MB jscpd tree into the npx cache on every cold runner
(~9s vs ~1s warm). setup-node's npm cache is keyed on package-lock.json,
which never changes for jscpd, so it can't keep this warm.
Add a dedicated actions/cache step that persists the npx cache directory,
keyed on OS, node version, and the jscpd DEFAULT_VERSION from src/lib.js.
Bumping the version naturally invalidates the cache.