test: force the smoke gate to fail, to watch it block a publish
Build images / sign-extension (push) Successful in 4s
CI / lint (push) Successful in 4s
CI / extension-version (push) Successful in 3s
Build images / build-ml (push) Successful in 7s
Build images / build-agent (push) Successful in 8s
CI / frontend-build (push) Successful in 19s
extension / lint (push) Successful in 18s
Build images / build-web (push) Successful in 7s
Build images / smoke-web (push) Skipped
Build images / promote (push) Skipped
CI / backend-lint-and-test (push) Successful in 31s
CI / integration (push) Successful in 1m57s
Build images / sign-extension (push) Successful in 4s
CI / lint (push) Successful in 4s
CI / extension-version (push) Successful in 3s
Build images / build-ml (push) Successful in 7s
Build images / build-agent (push) Successful in 8s
CI / frontend-build (push) Successful in 19s
extension / lint (push) Successful in 18s
Build images / build-web (push) Successful in 7s
Build images / smoke-web (push) Skipped
Build images / promote (push) Skipped
CI / backend-lint-and-test (push) Successful in 31s
CI / integration (push) Successful in 1m57s
TEMPORARY, reverted in the next commit. Milestone 362's verification section requires the gate to be seen rejecting a build — a gate nobody has watched reject anything is a gate nobody knows is wired up. Every real check passes, so the rejection has to be forced. Under test is the job dependency, not the assertions: a failed smoke-web must skip the promote job, and the three :latest tags must still name the digests they named before the run. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TTjbZZ6JirCMSaJzQV1RhA
This commit is contained in:
@@ -1214,6 +1214,18 @@ jobs:
|
||||
fi
|
||||
curl -fsS --max-time 5 "http://$WEB_IP:8080/api/health"
|
||||
echo
|
||||
|
||||
# >>> TEMPORARY — REVERTED IN THE NEXT COMMIT <<<
|
||||
# Milestone 362's verification says the gate must be watched
|
||||
# REJECTING a build before anyone can believe it is wired up. Every
|
||||
# real check above passes right now, so the only way to see a
|
||||
# rejection is to force one. What is under test here is the job
|
||||
# dependency, not the assertions: does a failed smoke actually stop
|
||||
# the promote, and does :latest stay where it was?
|
||||
echo "smoke: FORCED FAILURE — verifying the gate blocks the promote" >&2
|
||||
exit 1
|
||||
# >>> END TEMPORARY <<<
|
||||
|
||||
echo "smoke: all checks passed against $CANDIDATE"
|
||||
|
||||
# Move the channel tags — the whole point of the gate.
|
||||
|
||||
Reference in New Issue
Block a user