Check builds use Docker's cache: drop cache busting #177

Closed
opened 2026-11-16 22:11:38 +01:00 by clawbot · 1 comment
Collaborator

sneak, chat, 16 November about 21:15 UTC, on why check builds bust Docker's cache (#176): "there is no benefit to not using cache on unchanged trees"

Reworded: check builds use Docker's normal cache. A step reruns only when its inputs change; on an unchanged tree its stored result is reused. Nothing forces checks to rerun.

Work

  • Remove cache busting from the policy and the canonical files on next:
    • prompts/REPO_POLICIES.md: drop the requirement that check builds bust the cache, the CACHEBUST build argument, and the two rules that police it (scripts and ARG lines in one commit; a planted defect proving a changed check). Say instead that check builds use Docker's normal cache. Keep the rules that make reuse safe: pinned tools, lockfile hashes, -count=1 for tests.
    • The canonical script/lint, script/test, script/docker, script/cibuild and the canonical Dockerfile: drop --build-arg CACHEBUST=... and every ARG CACHEBUST line.
  • Leave apk add --no-cache alone: it is unrelated.
  • Spreading this to the repos that copy these files is #78; not this PR.

Definition of done

  • No CACHEBUST and no docker build --no-cache remain on next in the policy or the canonical files.
  • The policy says check builds use Docker's normal cache, in one or two plain sentences.
  • make check passes, and a second make check on the unchanged tree reuses the check steps.

Model: opus-5-5

sneak, chat, 16 November about 21:15 UTC, on why check builds bust Docker's cache (https://git.eeqj.de/sneak/prompts/issues/176): "there is no benefit to not using cache on *unchanged* trees" Reworded: check builds use Docker's normal cache. A step reruns only when its inputs change; on an unchanged tree its stored result is reused. Nothing forces checks to rerun. ## Work - Remove cache busting from the policy and the canonical files on `next`: - `prompts/REPO_POLICIES.md`: drop the requirement that check builds bust the cache, the `CACHEBUST` build argument, and the two rules that police it (scripts and `ARG` lines in one commit; a planted defect proving a changed check). Say instead that check builds use Docker's normal cache. Keep the rules that make reuse safe: pinned tools, lockfile hashes, `-count=1` for tests. - The canonical `script/lint`, `script/test`, `script/docker`, `script/cibuild` and the canonical `Dockerfile`: drop `--build-arg CACHEBUST=...` and every `ARG CACHEBUST` line. - Leave `apk add --no-cache` alone: it is unrelated. - Spreading this to the repos that copy these files is https://git.eeqj.de/sneak/prompts/issues/78; not this PR. ## Definition of done - No `CACHEBUST` and no `docker build --no-cache` remain on `next` in the policy or the canonical files. - The policy says check builds use Docker's normal cache, in one or two plain sentences. - `make check` passes, and a second `make check` on the unchanged tree reuses the check steps. Model: opus-5-5
Author
Collaborator

PR: #178 (branch issue-177-drop-cache-busting, base next).

Cache busting is removed from the policy, the four scripts and the Dockerfile. Judgement call: the README, the Go style guide and both checklists restated the old rules, so they are updated in the same commit.

Model: opus-5-5

PR: https://git.eeqj.de/sneak/prompts/pulls/178 (branch `issue-177-drop-cache-busting`, base `next`). Cache busting is removed from the policy, the four scripts and the `Dockerfile`. Judgement call: the README, the Go style guide and both checklists restated the old rules, so they are updated in the same commit. Model: opus-5-5
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/prompts#177