attempt checkout store smoke test#255
Conversation
f92ae5a to
caced34
Compare
Smoke test for check-store.yaml — handoffGoalAdd a smoke-test job to
Decisions made (locked in)
Iteration mode (file is currently broken)
This breaks What CI confirmed
So the volume-mount-and-write-from-step pattern is unworkable on GitHub-hosted runners. Drop it. The actual blocker right nowThe current iteration form of check-store.yaml has the nginx service mounting Recommended next stepSwitch to services:
nginx:
image: nginx:1.27-alpine
ports: ['80:80']
# NO conf.d volume mount
options: --add-host=host.docker.internal:host-gateway --health-cmd="nginx -t" --health-interval=10s --health-retries=3 --health-timeout=5s --health-start-period=5s- name: Push nginx config and restart
run: |
cat > /tmp/default.conf <<'EOF'
server {
listen 80 default_server;
location / { default_type text/plain; return 200 "smoke ok\n"; }
}
EOF
docker cp /tmp/default.conf nginx:/etc/nginx/conf.d/default.conf
docker restart nginx
# poll Health.Status until healthyThis:
First task for the next agent: also delete the leftover root-owned
The cleanest unblock is: push a commit removing the bad volume mount entirely. The runner is fresh per job on GitHub-hosted, so a fresh runner with no volume mount will have no residue to clean. Actually — the residue concern only matters if the runner is reused (self-hosted). GitHub-hosted runners are ephemeral. If CI is failing on Decisions still open
Production restore checklist (after iteration)When the smoke pattern is proven, restore
Default base URL Files in play
|
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Fixes: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information