Skip to content

Avrea Cache

Avrea Cache eliminates the network round-trips that slow down workflows on Avrea runners. Your builds hit caches colocated with your runners instead of fetching from remote storage. Workflows run directly by Avrea CI have separate cache support and limits.

For reusable job outputs, see the Avrea cache action guide for avrea-com/cache usage and migration from actions/cache. For dependency downloads and supported build outputs, prefer the automatic integrations below.

Five cache types work together, each targeting a different part of the pipeline:

GitHub Actions Cache

Drop-in replacement for GitHub's built-in cache. Works with actions/cache@v4+ and language setup actions. No workflow changes. Learn more →

Git Checkout Acceleration

Preloads repositories and eligible submodules from datacenter-local Git mirrors before actions/checkout runs. Learn more →

Git LFS Cache

Pull-through caching for large files stored with Git LFS. Repeated checkouts avoid downloading the same objects from GitHub again. Learn more →

Build Cache

Remote caching for build tools. Shares compilation artifacts across jobs and branches so rebuilds only recompile what changed. Learn more →

Package Cache

Pull-through proxy for package registries. Caches downloaded packages locally so npm install, pip install, and go mod download resolve instantly on repeat runs. Learn more →

All five caches run on the same infrastructure as your Avrea runners. When a workflow runs:

  1. GitHub Actions cache requests route to a local proxy instead of GitHub's remote storage.
  2. Git checkout prepares repositories from datacenter-local mirrors when enabled.
  3. Git LFS downloads pass through a repository-scoped local cache when enabled.
  4. Build tools (Go, Bazel, Gradle, etc.) are pre-configured to use a colocated remote cache.
  5. Package managers (npm, pip, Cargo, etc.) resolve through a local pull-through proxy.

No self-hosted infrastructure to manage. No S3 buckets to configure. Avrea handles storage, eviction, and lifecycle.

On Avrea runners, most caching is pre-configured:

LayerConfigurationWhat you do
GitHub ActionsFully automaticUse actions/cache@v4+ as normal
Git checkoutAutomatic when enabledTurn on Git Checkout Acceleration; keep using actions/checkout
Git LFSAutomatic when enabledTurn on Git LFS Cache; keep using Git LFS as normal
Build cacheEnvironment variables and config files injectedSome tools need minor workflow additions
Package cacheRegistry URLs pre-configuredPackage managers resolve through cache automatically

See the individual integration pages for tool-specific details.

Workflow runs and jobs show cache hit rates, bytes served and written, transfer errors, and supported build-client details. See Cache Stats for field definitions, coverage states, and the additional diagnostics available for GitHub Actions, package, Go, Xcode, and Gradle caches.

  • Default quota: 25 GB per repository for regular cache entries
  • Eviction: Least-recently-used entries are evicted when quota is exceeded
  • Retention: Unused entries become eligible for eviction after 7 days

Organization-private Swift package payloads use separate, organization-isolated artifact storage and do not count against the repository cache quota.

See Storage & Eviction for details.