clipper-registry/Clipper cache
Registry-backed cache volumes: lazily mount a clipper volume at a path on job start, push the changes back on job success. Chunk-level dedup means a warm push uploads only what changed.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| path | Directory to cache (mounted as a clipper volume). | yes | — |
| repo | Registry repository holding the cache tags (e.g. clipper.dev/org/ci-cache). | yes | — |
| key | Cache key prefix; the sanitized branch is appended. Mounts <key>-<branch> first, falls back to <key>-<base branch>, and pushes to <key>-<branch>. | yes | — |
| base-branch | Fallback lineage branch. Defaults to the pull request's base branch, else the repository's default branch. | no | "" |
| split-glob | Glob prefixes pushed as their own tar blobs (one per line), isolating churny subtrees so a warm push re-uploads KBs instead of whole blobs. | no | "" |
| cdc | Content-defined chunking on push. | no | true |
| jobs | Parallel transfer jobs for mount and push. | no | 16 |
| version | Clipper version to install (e.g. v0.28.0); latest by default. | no | latest |
Outputs
| name | description |
|---|---|
| cache-hit | Whether any tag mounted (false means cold start on a plain directory). |
| push-tag | The tag the post step pushes to (repo:key). |