-
Notifications
You must be signed in to change notification settings - Fork 56
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
trendline #183
Comments
closed as stale |
:) |
@roydekleijn Sorry, mate. We're trying our best to react to all the community feedback. As for today, the best way to contact the team is to create a discussion: https://github.com/orgs/allure-framework/discussions. We receive a notification to our Slack channel for each created discussion. Regarding your question: You're right; for Maven, you should copy the history manually. History was designed mainly for use in the CI environment, where the CI plugin will take care of it. It's been a while since then, and now we can see the community loves our history feature. There is definitely room for improvement. Can you please provide a few use cases when the Allure Maven plugin should handle the history? |
Hello,
I like to know how you go about with generating the trendline? So far I know there is some manual file copy step involved.
Steps I use now:
mvn clean test
mvn allure:report
cp -R target/site/allure-maven-plugin/history target/allure-results/
mvn test
mvn allure:report
This all works! I get a nice report including trendline. But,
mvn allure:report
it checks for the previous report and copies the files.I'm happy to hear from you, if step 2 should be implemented, I'm happy to help,
Roy
The text was updated successfully, but these errors were encountered: