Allure reports without running an Allure server

Allure's report is gorgeous — and traditionally trapped behind allure serve on someone's laptop, or a self-hosted server you now maintain. Generate the static report, ship the folder, done.

The artifact dead-end

allure serve spins up a local web server — useless for the teammate who just wants to see the failures. The 'proper' answer is hosting Allure Server or bolting S3 + Lambda + auth together, which is a lot of infrastructure for a test report.

But allure generate already emits a static site. Everything the server does for viewing, a plain static host does better — faster and with nothing to maintain.

Two lines to a live link

Build your output like you already do, then hand the folder to the action:

allure generate allure-results -o allure-report --clean

- uses: bitgate/ship-page-action@v1
  if: always()
  with:
    engine: allure

engine: allure makes the action find allure-report/ on its own — prefer explicit? path: allure-report/ does the same thing. Omit both and every known report gets probed; two or more matches land behind one URL with a built-in switcher. The link goes in the job summary — add comment: true and it lands on the pull request too.

What you get

• Suites, categories, history tabs and attachments render exactly as generated — the folder is served as-is
• Works for every Allure adapter — JUnit, TestNG, pytest, Playwright, Cucumber — they all emit the same static report
• Omit path entirely — the action auto-detects allure-report/

Questions

Need to share the report with someone outside GitHub? How to share a GitHub Actions artifact without a login.