CI/E2E: Upload website and backend container logs on failures

[Copilot]

Summary

E2E failures could hide runtime errors occurring inside containers; this adds direct access to website and backend logs from failed CI runs. The workflow now captures those container logs and publishes them as a downloadable artifact only on failure.

• Failure-only log capture
  • Add a CI step gated by failure() && !cancelled() to collect docker compose logs for website and backend.
• Downloadable diagnostics artifact
  • Upload /tmp/container-logs/ as container-logs (30-day retention), alongside the existing Playwright report.
• Scope
  • No changes to test execution paths; only post-failure observability in .github/workflows/e2e.yml.

- name: Collect website/backend container logs
  if: ${{ failure() && !cancelled() }}
  run: |
    mkdir -p /tmp/container-logs
    docker compose -f ../docker-compose.yml logs --no-color website > /tmp/container-logs/website.log || true
    docker compose -f ../docker-compose.yml logs --no-color backend > /tmp/container-logs/backend.log || true

Screenshot

N/A (CI workflow-only change)

PR Checklist

• All necessary documentation has been adapted.
• The implemented feature is covered by an appropriate test.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
dashboards	Ready	Preview, Comment	May 29, 2026 8:32am