Skip to content
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.

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

mvn allure:report allure:serve does not preserve report directory #139

Open
1 task done
theangrydev opened this issue Oct 27, 2020 · 3 comments
Open
1 task done

Comments

@theangrydev
Copy link

I'm submitting a ...

  • bug report

What is the current behavior?

When running mvn allure:report allure:serve the serve works correctly but the report is not preserved in the target directory. Running mvn allure:report alone correctly generates the report.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

Run mvn allure:report allure:serve

What is the expected behavior?

The reports directory should be preserved

What is the motivation / use case for changing the behavior?

There is no way to view the report that was generated by allure:report when it is used with allure:serve at the same time

Please tell us about your environment:

  • Allure version: 2.13.6
  • Generate report using: allure-maven@2.10.0
@smert0kotik
Copy link

same result for me using allure 2.8.1 and allure-maven@2.10.0 - using mvn allure:serve generates no reports and shows page withot data while they appear in allure-results folder

@MichaelRijsdijk
Copy link

MichaelRijsdijk commented Feb 25, 2022

I also faced this problem, but for me there is a solution and I think it would be for the others.

If you don't specify a location for the report to be generated OR you specify it in the same location as your allure-results it will generate the report in that location and the results will be lost. This results in what @smert0kotik describes, a no data report.

If you specify in the configuration of allure-maven plugin:
<reportDirectory>target/allure-report</reportDirectory>
It will work.

@CorwinSheffield
Copy link

Hello, I would like to bump this issue as I am experiencing the same. I think the culprit might be on line 100 of AllureCommandline.java

This line quietly deletes the path to the generated report before serving the report to the user. Would anything break if that line were removed and the configured report path is preserved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants