Caches

Caches

Transport temporary data between jobs using caching

Pipelines should assume that the cache must be rebuilt

The cache keyword defines what and when to push and pull

One job downloads or generates data and pushes to the cache

Subsequent jobs can pull from the cache to hit the ground running

Examples for many programming languages

Cache types

Local on the same runner with Docker or shell executor

Distributed with an S3-compatible backend (e.g. AWS S3 , MinIO , Ceph )

Hands-On

See chapter caches

Pro tip 1: Clear the cache

Clear the cache in two ways:

1. Change the cache key in your pipeline
2. On the pipeline page, click Clear runner caches in the upper right corner

Pro tip 2: Runner local cache

For some executors, the runner stores the cache locally when not configured otherwise

The local cache is located in the following directories:

• Shell: /home/gitlab-runner/cache/<user>/<project>/<cache-key>/cache.zip
• Docker: /var/lib/docker/volumes/<volume-id>/_data/<user>/<project>/<cache-key>/cache.zip