clawbot
9d68027287
check / check (push) Canceled after 0s
On sneak's ruling in #130, check builds may keep three more things besides Go's build cache. In each stage of the canonical Go Dockerfile, the system-package install and the module download now come before ARG CACHEBUST, so Docker keeps those layers until the base image, the install line, go.mod or go.sum changes. The modules are kept as a layer, not a cache mount, because Go does not check a cache mount's files again. golangci-lint run also mounts golangci-lint's cache. Every step that lints, tests or compiles still comes after ARG CACHEBUST and reruns on every check build, and both go test runs keep -count=1. The policy, both checklists, the Go style guide, the README and the script comments state the rule the same way. Model: opus-5-5
25 lines
937 B
Bash
Executable File
25 lines
937 B
Bash
Executable File
#!/bin/sh
|
|
# script/test: run the test suite. Testing is a phase of the Dockerfile
|
|
# and this builds that phase alone, on the same terms as script/lint:
|
|
# --target because a phase that is not the last stage is built only when
|
|
# named, and a new CACHEBUST value because a cached test layer is a test
|
|
# that did not run; unlike --no-cache, it keeps the layers above the ARG
|
|
# CACHEBUST line and the cache mounts. This relies on every stage of the
|
|
# Dockerfile declaring ARG CACHEBUST before every step that lints, tests
|
|
# or compiles; a stage without that line is served from cache on an
|
|
# unchanged tree, with no warning. --output type=cacheonly writes no
|
|
# image, since nothing uses one.
|
|
set -eu
|
|
|
|
SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd -P)"
|
|
ROOT="$(cd "$SCRIPT_DIR/.." && pwd -P)"
|
|
|
|
main() {
|
|
cd "$ROOT"
|
|
docker build --build-arg CACHEBUST="$(date +%s)-$$" \
|
|
--target test \
|
|
--output type=cacheonly .
|
|
}
|
|
|
|
main "$@"
|