During pipeline execution, many dependencies and intermediate artifacts are generated. Caching these for reuse in subsequent pipelines can significantly reduce build time.

Runner Node Caching

To balance single-point-of-failure risks with cache hit rates, pipelines are assigned to 3 fixed runner nodes by default (the number adjusts dynamically with resource usage).

Tips

Node assignments are not permanent — they may change as the platform scales.

Code Caching

When a pipeline executes, it automatically pulls code to the runner node and caches it for reuse by subsequent pipelines.

File Caching

During builds, files like project dependencies and build caches can be cached on the runner node for reuse by subsequent pipelines.

Configuration reference: pipeline.runner.volumes

Tips

Leveraging OverlayFS instant-copy technology, caches can be efficiently reused under high concurrency.

Cross-Node Caching

To share the same cache across all runner nodes, you can build Docker cache images containing the content to be cached.

Specific methods reference the built-in task: docker:cache

Previous pagePipeline Visualization

Next pageScheduled Tasks