feat: add Allure reports to GH pages #2393
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Job Summary for GradleBuild and test :: BuildAndPackageWithUnitTests
|
|
Central Server Allure report: https://nordic-institute.github.io/X-Road/central-server/ui-system-test/1096 |
Job Summary for GradleBuild and test :: BuildAndPackageWithUnitTests
|
|
E2E Allure report: https://nordic-institute.github.io/X-Road/e2e/1097 |
|
Central Server Allure report: https://nordic-institute.github.io/X-Road/central-server/ui-system-test/1097 |
|
Security Server Allure report: https://nordic-institute.github.io/X-Road/security-server/system-test/1097 |
raits
changed the title
.github/workflows/build.yaml
Outdated
| issue_number: context.issue.number, | ||
| owner: context.repo.owner, | ||
| repo: context.repo.repo, | ||
| body: 'E2E Allure report: https://nordic-institute.github.io/X-Road/e2e/${{ github.run_number }}' |
There was a problem hiding this comment.
perhaps opening in a new tab would be preferred?
There was a problem hiding this comment.
Based on what I found searching the topic it seems that this is not possible in GitHub comments.
|
There are few other places with allure reports, were those intentionally skipped or just missed? Would it be possible to consolidate all links into a single comment with a table? Maybe persist links into action runtime and create comment as a final step? Also just a note: by generating report instead of using report generated by gradle, we loose execution logs tab which is a customization to see logs during whole execution. Maybe zipping those logs and adding DL link to the same report table would suffice. |
Job Summary for GradleBuild and test :: BuildAndPackageWithUnitTests
|
Job Summary for GradleBuild and test :: BuildAndPackageWithUnitTests
|
Job Summary for GradleBuild and test :: BuildAndPackageWithUnitTests
|
Job Summary for GradleBuild and test :: BuildAndPackageWithUnitTests
|
Job Summary for GradleBuild and test :: BuildAndPackageWithUnitTests
|
Job Summary for GradleBuild and test :: BuildAndPackageWithUnitTests
|
Job Summary for GradleBuild and test :: BuildAndPackageWithUnitTests
|
Job Summary for GradleBuild and test :: BuildAndPackageWithUnitTests
|
Job Summary for GradleBuild and test :: BuildAndPackageWithUnitTests
|
Job Summary for GradleBuild and test :: BuildAndPackageWithUnitTests
|
Job Summary for GradleBuild and test :: BuildAndPackageWithUnitTests
|
Job Summary for GradleBuild and test :: BuildAndPackageWithUnitTests
|
Job Summary for GradleBuild and test :: BuildAndPackageWithUnitTests
|
Job Summary for GradleBuild and test :: BuildAndPackageWithUnitTests
|
Job Summary for GradleBuild and test :: BuildAndPackageWithUnitTests
|
Job Summary for GradleBuild and test :: BuildAndPackageWithUnitTests
|
|
Job Summary for GradleBuild and test :: BuildAndPackageWithUnitTests
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support to generating Allure reports from results produced during the build, publishing them with history to GH pages and leaving the links as comments.
Unfortunately, it doesn't seem that extensions are currently supported by the action: https://github.com/simple-elf/allure-report-action.