CI Runnerscirunners.org
Glossary

What is dependency cache?

Answer in brief

A store that saves downloaded packages and build outputs between CI jobs, keyed by a hash, so later jobs can restore them instead of redoing the work.

By the CI Runners editors · Updated

Dependency cache in CI

CI jobs repeat expensive steps: downloading npm, Maven, pip or Cargo packages and compiling unchanged code. A dependency cache saves those directories under a key, usually a hash of the lockfile, and restores them in later jobs. In GitHub Actions this is the actions/cache action; GitLab CI has a cache keyword.

How much a cache helps depends on how quickly it restores. A large cache fetched over a slow link can take as long as the install it replaces, which is why third-party runners often run their own cache backend in the same data centre as the runners.

Sources

  1. docs.github.com/en/actions/reference/workflows-and-actions/dependency-caching

Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 22, 2026. Confirm anything that matters in the provider’s own documentation.

Cite this page

CI Runners. (2026). What is dependency cache?. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/glossary/dependency-cache/