Archive the current build’s cache entries

Save only the cache entries the current build uses.

Prompt

Evaluate and apply this CI technique to my repository: Archive the current build’s cache entries.

Save only the cache entries the current build uses.

Read the technique and its source-backed company examples: https://starsling.dev/ci-playbooks/techniques/compact-cache-contents.md

Inspect this repository’s CI workflows, build and test commands, dependencies, and recent run timings. Identify where this technique applies and explain the expected benefit using this repository’s evidence.
Measure a baseline from recent comparable runs: elapsed time, queue time, runner minutes and failures where available. If data is unavailable, say what cannot be measured.
Compare relevant company approaches, checking prerequisites, platform differences and tradeoffs. Rank applicable options by evidence, fit and measurable opportunity; do not present company results as predictions for this repo.
Recommend the smallest safe change, show what checks and fallback paths remain, and ASK ME WHICH CHANGE TO APPROVE BEFORE EDITING ANY FILES.
Only after approval, work on a new feature branch, make one reversible change, and open a reviewable pull request. Never merge or push to a default or protected branch.
Keep required checks, test coverage, deployment and release behavior intact. Validate the change and compare equivalent runs where possible; report limitations and what should be monitored after merge.

View all playbooks

How OpenAI used this technique

Read what OpenAI changed and follow the original sources.

Archive the current build’s cache entries

The Java SDK stopped archiving every historical Gradle task-cache entry and saves only the entries its current build graph produces. Restored entries are imported into the normal cache, and a fresh collector directory keeps history out of the next save.

Retained cache payload: from a 3,326,734,224-byte history archive to a 123,910,919-byte current-run artifact Source

Use it when: A build cache accumulates far more history than the current build consumes.
Before applying it: A smaller cache serves fewer other branches, and a new namespace starts cold.

How OpenAI used this technique

Archive the current build’s cache entries

Company Playbooks