bilhej/.forgejo/workflows
Joakim Mörling e4de2a316a
All checks were successful
CI / Lint, type check, unit tests, coverage (push) Successful in 1m47s
CI / E2E browser tests (push) Successful in 43s
fix: health check false-negative + add rollback on failure
The deploy pipeline had two critical bugs:

1. Health check used /api/vehicles/ZZZ999 with curl -f. This endpoint
   returns HTTP 404 for unknown plates (correct behavior), which curl -f
   treated as a failure. The backend was actually healthy.
   Fix: use /api/vehicles/ABC123 (seeded in V6 migration, always 200)
   and remove -f flag from curl.

2. No rollback on failure. If health checks failed, containers stayed
   running forever because the pipeline exited 1 without stopping them.
   Fix: combine health checks into one step. If either fails, run
   'docker compose down' (without -v, so DB volume is preserved) before
   exiting with failure.
2026-05-20 13:02:56 +02:00
..
ci.yml ci: fix coverage summary table — remove Status column and trailing empty cell 2026-05-19 20:40:26 +02:00
deploy.yml fix: health check false-negative + add rollback on failure 2026-05-20 13:02:56 +02:00