Skip to content

Managing Cache

Go to Settings > Usage > Cache in the Avrea console. The overview lists each repository's usage against its quota and, where entries were recently evicted, its retention. Select a repository to see:

  • Usage per cache type (gha, go-build, bazel-build, sccache-build, etc.)
  • Retention: how long an unused entry stays cached before it is evicted to keep the repository within its quota. See Sizing your cache for how to read it.
  • Cache traffic from the last 24 hours. Workflow run and job pages provide the same stats scoped to one execution. See Cache Stats to interpret hit rates, transfers, errors, diagnostics, and coverage states.

Organization admins can also purge all of a repository's cache entries there. A purge is rarely needed: a full cache is normal, and the least recently used entries are evicted automatically.

Terminal window
avr cache usage --repo rep-abc123

Shows the cache usage summary for a repository. To list individual entries, with their size, hits, and last-used time:

Terminal window
avr cache list --repo rep-abc123

The CLI's Hits column and the cache API's hit_count report approximate storage-read activity, not completed restores. Successful HEAD requests and each full or ranged GET request count separately, so one restore can add multiple hits. Reprocessed access records can also be counted again. Entries created before this counting change can include historical totals counted once per key per log file. Use this value as an activity indicator, not a restore success rate; it does not determine eviction order.

To inspect or delete individual entries, use the CLI:

Terminal window
avr cache delete --repo rep-abc123 --type gha --key "node_modules"
avr cache delete --repo rep-abc123 --all

Each cache type can be configured at the organization or repository level.

Go to Settings in the Avrea console to toggle caches on or off:

SettingDescriptionDefault
GitHub Actions CacheCache dependencies and build outputs via actions/cacheOn
GitHub Actions Action CacheServe the action archives a workflow pulls with uses: from datacenter-local storageOff
Git Checkout AccelerationPreload workflow repositories from datacenter-local Git mirrorsOff
Git Submodule PrecheckoutChoose root-only, top-level, or recursive preloadingRoot only
Git LFS CacheCache Git LFS downloads in datacenter-local storageOff
Go Build CacheAccelerate Go builds with shared GOCACHEPROGOn
Bazel Remote CacheAccelerate Bazel builds with a shared remote cacheOn
Turborepo CacheCache Turborepo task outputs across workflow runsOn
ccacheAccelerate C/C++ compilations with shared ccache storageOn
Gradle Build CacheShare Gradle build outputs across workflow runsOn
sccacheAccelerate Rust and C/C++ compilations with shared sccacheOn
Maven Build CacheShare Maven build outputs across workflow runsOn
sbt Build CacheShare sbt build outputs across workflow runsOn
Nix Binary CacheCache Nix build outputs as a binary cacheOn
Nx Remote CacheCache Nx task outputs across workflow runsOn
Package Manager CacheMaster switch for package caching, including Swift, Playwright, Puppeteer, Electron, Cypress, and SeleniumOn
Playwright Browser CacheCache Playwright browser downloads; requires Package Manager CacheOn
Puppeteer Browser CacheCache Puppeteer Chrome and headless-shell downloads; requires Package Manager CacheOn
Electron Binary CacheCache Electron releases and checksums; requires Package Manager CacheOn
Cypress Binary CacheCache Cypress binary archives; requires Package Manager CacheOn
Selenium Browser & Driver CacheCache Selenium browser and driver downloads; requires Package Manager CacheOn
Operating System Package CacheConfigure Ubuntu runner apt caching; independent of Package Manager Cache; containers opt in separatelyOn
Swift Package RegistryResolve public SwiftPM dependencies through Avrea's registryOn
Private Swift PackagesResolve eligible organization-private Swift packages through Avrea's registryOff
Xcode Compilation CacheReuse compiler outputs across macOS workflow runsOn
Tuist Module CacheShare Tuist module artifacts across macOS runnersOff

Organization-level settings apply to all repositories by default. Repository-level overrides take precedence.

The GitHub Actions Action Cache is the exception if your organization uses organization-level runners. A runner downloads every uses: action while setting up the job, before it knows which repository the job belongs to, so only the organization-level value applies. The repository settings page shows the setting read-only there, and a repository-level write is rejected.

List current settings:

Terminal window
avr settings list

Disable a specific cache for a repository:

Terminal window
avr settings set cache.sccache.enabled false

Re-enable it:

Terminal window
avr settings set cache.sccache.enabled true

Reset to the inherited default:

Terminal window
avr settings reset cache.sccache.enabled

View all available setting definitions:

Terminal window
avr settings schema