shankar0123 69266c8ed2 ci: dump container logs on deploy-vendor-e2e failure ...

The 25194251740 CI run failed with "container certctl-test-server is
unhealthy" but the GitHub Actions log doesn't include the server's
stdout/stderr — compose only reports the dependency-chain symptom.
Without the server's actual log output we can't tell whether the
unhealthy state was caused by a DB migration crash, port bind
failure, entrypoint stall, OOM kill, or healthcheck race.

Add an `if: failure()` step right before teardown that dumps:

  - `docker compose ps -a` (every container's exit status)
  - last 200 lines from certctl-test-server
  - all of tls-init (one-shot, short)
  - last 100 lines from postgres + stepca + agent
  - last 50 lines from pebble

This is a permanent debuggability improvement, not a band-aid:
the matrix-collapse (Phase 5) brings up ~18 containers concurrently
where pre-collapse the per-vendor matrix brought up ~7. Future
transient failures will be much faster to diagnose with logs in
the CI output. Once we know the actual root cause from this dump,
we fix it for real.

Placed AFTER skip-count enforcement (so failures in either step
trigger it) and BEFORE teardown (which is `if: always()` and would
otherwise nuke the containers before we could log them).

2026-04-30 23:37:05 +00:00

..

workflows

ci: dump container logs on deploy-vendor-e2e failure

2026-04-30 23:37:05 +00:00

coverage-thresholds.yml

ci-pipeline-cleanup Phase 2: coverage thresholds → YAML manifest

2026-04-30 20:39:30 +00:00