Skip to content

Replace allure javascript config with a static configuration file #1501

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
andrcuns wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Replace allure javascript config with a static configuration file #1501

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions .github/workflows/build.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ jobs:

- uses: actions/setup-node@v7
with:
node-version: '20.x'
node-version: '24.x'

- name: "Set up JDK"
uses: actions/setup-java@v6
Expand Down Expand Up @@ -70,7 +70,7 @@ jobs:

- name: "Run tests with Allure"
if: always()
run: npx -y allure@3 run --config ./allurerc.mjs --rerun 2 --environment="${{ env.ALLURE_MATRIX_ENV }}" --dump="${{ env.ALLURE_TEST_DUMP_NAME }}" -- ./gradlew --no-build-cache cleanTest test $GRADLE_EXCLUDES
run: npx -y allure@3 run --config ./allurerc.yaml --rerun 2 --environment="${{ env.ALLURE_MATRIX_ENV }}" --dump="${{ env.ALLURE_TEST_DUMP_NAME }}" -- ./gradlew --no-build-cache cleanTest test $GRADLE_EXCLUDES

- name: "Upload Allure test dump"
if: always()
Expand Down Expand Up @@ -98,7 +98,7 @@ jobs:

- uses: actions/setup-node@v7
with:
node-version: '20.x'
node-version: '24.x'

- name: "Download Allure dumps"
uses: actions/download-artifact@v8
Expand All @@ -109,7 +109,7 @@ jobs:
merge-multiple: true

- name: "Generate Allure report"
run: npx -y allure@3 generate --config ./allurerc.mjs --dump="allure-results-*.zip" --output=./build/allure-report
run: npx -y allure@3 generate --config ./allurerc.yaml --dump="allure-results-*.zip" --output=./build/allure-report

- name: "Post Allure summary"
if: github.event_name == 'pull_request' && github.event.pull_request.head.repo.fork == false
Expand Down
27 changes: 0 additions & 27 deletions allurerc.mjs
View file
Open in desktop

This file was deleted.

14 changes: 14 additions & 0 deletions allurerc.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
name: Allure Java
output: ./build/allure-report
plugins:
awesome:
options:
groupBy:
- module
appendTitlePath: true
publish: true
testops:
options:
launchName: "${{ 'Allure Java GitHub actions run (' + date.iso + ')' }}"
allureService:
accessToken: "${{ has(env.ALLURE_SERVICE_TOKEN) ? env.ALLURE_SERVICE_TOKEN : '' }}"

@baev baev Nov 6, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is the point of this condition?

@andrcuns andrcuns Nov 6, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To make it optional. The underlying parser raises error if environment variable it references is missing by default, it doesn't return undefined like pure javascript would

6 changes: 3 additions & 3 deletions docs/allure-agent-mode.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,9 +50,9 @@ Refresh this section when Allure, Gradle, test runners, Allure results paths, re
- Result-path configuration: module `src/test/resources/allure.properties` files set `allure.results.directory=build/allure-results`.
- Project labels: most modules set `allure.label.epic=#project.description#` and `allure.label.module=<module-name>` in `allure.properties`.
- Issue-link patterns: some modules define `allure.link.issue.pattern=https://github.com/allure-framework/allure-java/issues/{}`.
- Report config: `allurerc.mjs` configures the generated report name, output, grouping by module, publishing, and optional Allure Service token.
- CI Allure execution: `.github/workflows/build.yml` runs `npx -y allure@3 run --config ./allurerc.mjs --rerun 2 --environment=<matrix-env> --dump=<dump-name> -- ./gradlew --no-build-cache cleanTest test`.
- CI report generation: `.github/workflows/build.yml` downloads Allure dumps, runs `npx -y allure@3 generate --config ./allurerc.mjs --dump="allure-results-*.zip" --output=./build/allure-report`, and posts a PR summary for same-repository pull requests.
- Report config: `allurerc.yaml` configures the generated report name, output, grouping by module, publishing, and optional Allure Service token.
- CI Allure execution: `.github/workflows/build.yml` runs `npx -y allure@3 run --config ./allurerc.yaml --rerun 2 --environment=<matrix-env> --dump=<dump-name> -- ./gradlew --no-build-cache cleanTest test`.
- CI report generation: `.github/workflows/build.yml` downloads Allure dumps, runs `npx -y allure@3 generate --config ./allurerc.yaml --dump="allure-results-*.zip" --output=./build/allure-report`, and posts a PR summary for same-repository pull requests.

## Project Test-Design Conventions

Expand Down
Loading