check / check (push) Failing after 2s
script/cibuild, script/docker, script/lint and script/test passed the tag from script/projectname inline to docker build, where a failing command substitution does not trip set -e. Each now assigns it to `tag` on its own line first, so the script stops where script/projectname fails. The comment above it says why; the REPO_POLICIES.md snippets show the same form. Model: opus-5-5
28 lines
948 B
Bash
Executable File
28 lines
948 B
Bash
Executable File
#!/bin/sh
|
|
# script/lint: run the linter. Linting is a phase of the Dockerfile and
|
|
# this builds that phase alone; the linter is never installed or run on
|
|
# a developer host, where a shared result cache and a host-global lock
|
|
# make its answer untrustworthy.
|
|
#
|
|
# The phase is not the last stage in the file, so it is built only when
|
|
# --target names it. --no-cache because a cached lint layer is a lint
|
|
# that did not run. The tag makes each build replace the previous image
|
|
# instead of leaving a dangling one behind.
|
|
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 lint \
|
|
-t "$tag-lint" .
|
|
}
|
|
|
|
main "$@"
|