Codefresh: pipeline cache lives on the shared volume, clone purges files

Codefresh: pipeline cache lives on the shared volume, clone purges files

TL;DR

If a Codefresh pipeline cache miss makes no sense, look at the shared volume lifecycle, not the cache config. Files outside .gitignore get purged on clone, and parallel builds can start from a fresh volume. Context: From the official Codefresh pipeline caching docs.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

The pipeline cache is tied to the shared volume, not to the pipeline definition. The clone step purges files that are not in .gitignore, and concurrent builds can start with a fresh volume, so cached files you expected to be there may be gone. People debug their cache steps when the real culprit is the volume lifecycle.

Source: From the official Codefresh pipeline caching docs. The pipeline cache is tied to the shared volume, not to the pipeline definition. The clone step purges files that are not in .gitignore, and concurrent builds can start with a fresh volume, so cached files you expected to be there may be gone. People debug their cache steps when the real culprit is the volume lifecycle.

Verified resolution: If a Codefresh pipeline cache miss makes no sense, look at the shared volume lifecycle, not the cache config. Files outside .gitignore get purged on clone, and parallel builds can start from a fresh volume.

Source URL: https://github.com/codefresh-io/docs.codefresh.io/blob/HEAD/_docs/pipelines/pipeline-caching.md