Repository navigation
docs(build): document the temporary no-cache on docker builds - #955
Conversation
The no-cache/pull flags changed behaviour for every caller of build.yml and docker-build-ts, but the docs still promised layer reuse: docs/build.md said the identity-verification layers land in the Actions cache so the push build reuses them, and the composite README said nothing at all. Add a "Layer cache — temporarily disabled" section to both, naming what it costs callers (no layer reuse, cache-from reads nothing while cache-to keeps writing, no input added or removed) and pointing at #953 for the revert.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughThe documentation describes temporary Docker layer-cache disabling with ChangesDocker build cache documentation
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~4 minutes Change: Other Possibly related issues
Suggested reviewers: Merge Risk: ⚪ Minimal · up to
|
🔍 PR Validation Summary✅ PR Mergeable — no blocking failures
|
🔍 Lint Analysis
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
The section said "the build step" and "builds are therefore slower", but the composite has two mutually exclusive build steps and only the push one carries no-cache/pull. Name the push step, and say why the dry-run step is left alone: push: false, no cache-to, so nothing it builds reaches a published image or seeds the cache the push build reads. docs/build.md needs no equivalent change — in build.yml both steps, including the push: false identity-verification build whose layers feed the push through the GHA cache, carry the flags.
|
@coderabbitai review |
✅ Action performedReview finished.
|
GitHub Actions Shared Workflows
Description
Documentation follow-up to #954, which is already merged and released in v1.87.1. That PR set
no-cache: true+pull: trueon thedocker/build-push-actionsteps inbuild.ymland in thedocker-build-tscomposite, so a cached rebuild stops replaying the oldapk/aptlayer and shipping the vulnerableca-certificates. This PR contains no workflow changes — only the docs that the behaviour change left stale.docs/build.mdsrc/build/docker-build-ts/README.mddocs/build.mdclaimed the identity-verification layers land in the Actions cache so the push build reuses them for that platform instead of compiling it twice. Withno-cachethat is false, and nothing told callers that their builds had lost layer reuse, or why.The new section states what the measure costs: no layer is reused,
cache-from: type=ghareads nothing whilecache-tokeeps writing, and no input was added or removed, so nothing changes in how the workflow is called. It points at #953 for the revert.Type of Change
feat: New workflow or new input/output/step in an existing workflowfix: Bug fix in a workflow (incorrect behavior, broken step, wrong condition)perf: Performance improvement (e.g. caching, parallelism, reduced steps)refactor: Internal restructuring with no behavior changedocs: Documentation only (README, docs/, inline comments)ci: Changes to self-CI (workflows under.github/workflows/that run on this repo)chore: Dependency bumps, config updates, maintenancetest: Adding or updating testsBREAKING CHANGE: Callers must update their configuration after this PRBreaking Changes
None. No executable file is touched.
Testing
@this-branchor the beta tagDocumentation only — no run to link. The behaviour it describes shipped in #954 / v1.87.1.
Related Issues
Documents the measure tracked for revert in #953. Follow-up to #954.