Cache dependencies and build outputs in GitHub Actions
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
Go to file
Brenden Matthews 7994cabd39
Add support for S3 endpoints
8 months ago
.devcontainer GA for granular cache (#1035) 3 years ago
.github Rename workflow file for tests 1 year ago
.licenses/npm licensed cache 2 years ago
.vscode Initial commit 6 years ago
__tests__ Add test case for process exit 2 years ago
dist Add support for S3 endpoints 8 months ago
restore Update "only-" actions to node20 2 years ago
save Update "only-" actions to node20 2 years ago
src Add support for S3 endpoints 8 months ago
.eslintrc.json Update eslint and prettier 4 years ago
.gitattributes Fix line ending for windows test 4 years ago
.gitignore test e2e during workflow (#185) 6 years ago
.licensed.yml Add Licensed to attribute third party licenses 5 years ago
.prettierrc.json Initial commit 6 years ago
CODE_OF_CONDUCT.md Fix repo name in contact email (#41) 6 years ago
CONTRIBUTING.md Update contributing.md 5 years ago
LICENSE Initial commit 6 years ago
README.md Add support for S3 endpoints 8 months ago
RELEASES.md Bump version 2 years ago
action.yml action.yml and readme 2 years ago
caching-strategies.md Fixing paths for OSes (#1101) 3 years ago
examples.md Clarify that macos-latest image has bazelisk 3 years ago
jest.config.js Resolve dependabot alerts 4 years ago
package-lock.json Merge remote-tracking branch 'upstream/main' into fix/v4-update 1 year ago
package.json Merge remote-tracking branch 'upstream/main' into fix/v4-update 1 year ago
tips-and-workarounds.md Merge branch 'main' into pdotl-patch-1 3 years ago
tsconfig.json Initial commit 6 years ago

README.md

Shockingly faster cache action

This action is a drop-in replacement for the official actions/cache@v4 action, for use with the RunsOn self-hosted GitHub Action runner provider, or with your own self-hosted runner solution.

image

It will automatically store your caches in a dedicated RunsOn S3 bucket that lives close to your self-hosted runners, ensuring you get at least 200MiB/s download and upload throughput when using caches in your workflows. The larger the cache, the faster the speed.

Also note that you no longer have any limit on the size of the cache. The bucket has a lifecycle rule to remove items older than 10 days.

If no S3 bucket is provided, it will also transparently switch to the default behaviour. This means you can use this action and switch between RunsOn runners and official GitHub runners with no change.

Usage with RunsOn

If using RunsOn, simply replace actions/cache@v4 with runs-on/cache@v4. All the official options are supported.

- - uses: actions/cache@v4
+ - uses: runs-on/cache@v4
    with:
      ...

Please refer to actions/cache for usage.

Usage outside RunsOn

If you want to use this in your own infrastructure, setup your AWS credentials with aws-actions/configure-aws-credentials, then:

  - uses: aws-actions/configure-aws-credentials@v4
    ...
  - uses: runs-on/cache@v4
    with:
      ...
    env:
      RUNS_ON_S3_BUCKET_CACHE: name-of-your-bucket

Be aware of S3 transfer costs if your runners are not in the same AWS region as your bucket.

Special environment variables

  • RUNS_ON_S3_BUCKET_CACHE: if set, the action will use this bucket to store the cache.
  • RUNS_ON_S3_BUCKET_ENDPOINT: if set, the action will use this endpoint to connect to the bucket. This is useful if you are using AWS's S3 transfer acceleration or a non-AWS S3-compatible service.
  • RUNS_ON_RUNNER_NAME: when running on RunsOn, where this environment variable is non-empty, existing AWS credentials from the environment will be discarded. If you want to preserve existing environment variables, set this to the empty string "".
  • RUNS_ON_S3_FORCE_PATH_STYLE or AWS_S3_FORCE_PATH_STYLE: if one of those environment variables equals the string "true", then the S3 client will be configured to force the path style.