Aggregate Allure Report to a Single Report (incl. history)

[phammer]

We have a multi-module Java projects, thus allure is executed in the sub-projects. Locally, I've done a quick prototype of a shell script bulling everything together and keeping a history.

However, would be beautiful and super useful to have that in your nice Github action properly done rather than this manual approach.

#!/bin/bash

# Create combined results directory
mkdir -p combined-allure-results

# Copy history from previous report (if it exists)
if [ -d "allure-report/history" ]; then
  cp -R allure-report/history combined-allure-results/
fi

# Copy results from all modules with prefixes
allure generate modules/app/allure-results --clean -o combined-allure-results --allure-results-prefix app_
allure generate modules/formatter/allure-results --clean -o combined-allure-results --allure-results-prefix formatter_
allure generate modules/utils/allure-results --clean -o combined-allure-results --allure-results-prefix utils_
allure generate modules/testUtils/allure-results --clean -o combined-allure-results --allure-results-prefix testUtils_

# Generate final report
allure generate combined-allure-results --clean -o allure-report

# Open the report
allure open allure-report

In its core, we have a Java/Spring project. But I don't think that matters. Also, I know there is a gradle allureAggegrateReport project, but that doesn't do the job and it would be Java/Grade specific. Sticking to shell makes sense.

[jamesquantum]

+1 this issue

[renatafaracobah]

+1

[OleksandrOwl]

+1

[cybersokari]

@phammer While waiting, try allure-deployer-action. It allows comma-separated allure results paths for report Aggregation

[phammer]

thx for the feedback @cybersokari . I've switched to a command-line based approach instead for now.