The weekly refresh now publishes only what a gate has proven — and a new install can start #249
@@ -1215,17 +1215,6 @@ jobs:
|
|||||||
curl -fsS --max-time 5 "http://$WEB_IP:8080/api/health"
|
curl -fsS --max-time 5 "http://$WEB_IP:8080/api/health"
|
||||||
echo
|
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"
|
echo "smoke: all checks passed against $CANDIDATE"
|
||||||
|
|
||||||
# Move the channel tags — the whole point of the gate.
|
# Move the channel tags — the whole point of the gate.
|
||||||
|
|||||||
Reference in New Issue
Block a user