chore(ci): clarify Docker curl retry intent

This commit is contained in:
Tam Nhu Tran
2026-05-22 11:14:51 -04:00
parent e7fed040ee
commit d79e35b0c8
2 changed files with 6 additions and 0 deletions
+4
View File
@@ -376,6 +376,8 @@ jobs:
- name: Probe dashboard port 3000
run: |
# Single-shot probe by design: healthcheck and network-contract already
# handle readiness waits, and curl --retry would not retry HTTP errors.
HTTP_CODE=$(curl -o /dev/null -s -w "%{http_code}" --max-time 10 http://127.0.0.1:13000/ || echo "000")
if [[ "${HTTP_CODE}" == "000" ]]; then
echo "[X] Could not reach dashboard on :3000 (connection failed)"
@@ -385,6 +387,8 @@ jobs:
- name: Probe CLIProxy port 8317
run: |
# Single-shot probe by design: healthcheck and network-contract already
# handle readiness waits, and curl --retry would not retry HTTP errors.
HTTP_CODE=$(curl -o /dev/null -s -w "%{http_code}" --max-time 10 http://127.0.0.1:18317/ || echo "000")
if [[ "${HTTP_CODE}" == "000" ]]; then
echo "[X] Could not reach CLIProxy on :8317 (connection failed)"
@@ -31,6 +31,8 @@ jobs:
- name: Download compose from canonical URL
run: |
# Keep this as a plain fetch. curl --retry only covers transport-like
# failures by default and can overstate HTTP 5xx resilience.
curl -fsSL https://ccs.kaitran.ca/docker-compose.yaml -o /tmp/ccs-compose.yaml
echo "--- downloaded compose ---"
cat /tmp/ccs-compose.yaml