fix: stabilize compose e2e lifecycle #79
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "codex/stabilize-compose-e2e"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
docker compose up --exit-code-from e2e-runnerinstead of a separate one-offdocker compose runuptime-kumaande2e-runnerin one Compose lifecycle with the existing health dependency3001:3001publish from the root E2E Compose fileWhy
The intermittent failure was
curlexit 6 forhttp://uptime-kuma:3001, which is DNS resolution failure inside the runner container, not slow Uptime Kuma startup. A larger readiness timeout would only wait longer for a broken Compose DNS path.Verification
docker compose -p ci-up-shape-fresh-branch -f docker-compose.yaml --profile e2e up --build --abort-on-container-exit --exit-code-from e2e-runner e2e-runnerjust format && just everythingjust checkgit diff --check HEAD~1..HEAD