Files
crowdsec-bouncer-traefik-pl…/.github/workflows/e2e.yml
T
mhxandClaude Opus 4.8 33def87c30 ♻️ tests: run e2e suite in a single sequential job
The matrix spawned one runner per scenario, so the Traefik, Crowdsec and
whoami images were pulled — and Crowdsec booted — once per scenario. Run
the whole suite in a single job with `make -k e2e` instead: Docker caches
the images locally so they are pulled only once, and `-k` keeps the
remaining scenarios running after a failure (make still exits non-zero).

Scenarios already share the canonical `crowdsec` container name and the
8000 port, so they were meant to run sequentially anyway.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-06 12:03:19 +02:00

35 lines
901 B
YAML

name: E2E
on:
push:
branches: [main]
pull_request:
concurrency:
group: e2e-${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
e2e:
name: e2e
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v6
# A single runner runs every scenario sequentially. Docker caches the
# Traefik/Crowdsec/whoami images locally, so they are pulled only once
# for the whole suite instead of once per scenario. `-k` keeps going
# after a failing scenario so the logs cover all of them, while make
# still exits non-zero if any scenario failed.
- name: Run scenarios
run: make -k e2e
- name: Upload logs on failure
if: failure()
uses: actions/upload-artifact@v4
with:
name: e2e-logs
path: /tmp/e2e-*.log
if-no-files-found: ignore