clawbot
b09fff488b
check / check (push) Successful in 49s
`script/cibuild`, `script/docker`, `script/lint` and `script/test` passed the image tag from `script/projectname` inline in the `docker build` arguments. A failing command substitution inside an argument does not trip `set -e`, so the scripts went on to `docker build` with an empty, `-lint` or `-test` tag, against the rule their own comment states. Each now assigns `tag` on its own line before `docker build`, so the script stops where `script/projectname` fails. The snippets in `prompts/REPO_POLICIES.md` show the same form, and the policy states the own-line rule. Consuming repositories pick this up on their next re-vendor; the defect failed closed. Model: opus-5-5
24 lines
786 B
Bash
Executable File
24 lines
786 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, --no-cache because a cached test layer is a test that did not
|
|
# run, and a tag so each build replaces the previous image.
|
|
set -eu
|
|
|
|
SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd -P)"
|
|
ROOT="$(cd "$SCRIPT_DIR/.." && pwd -P)"
|
|
|
|
main() {
|
|
cd "$ROOT"
|
|
# The tag gets its own line: a failing command substitution inside
|
|
# an argument does not trip `set -e`, so the inline form degrades
|
|
# silently to an empty constant.
|
|
tag="$("$SCRIPT_DIR/projectname")"
|
|
docker build --no-cache \
|
|
--target test \
|
|
-t "$tag-test" .
|
|
}
|
|
|
|
main "$@"
|