-
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
Can we create allure report outside the target directory. #45
Comments
Yeah, you can configure report directory using <configuration>
<reportDirectory>allure-report</reportDirectory>
</configuration> Also you can use our Gitter char for such questions https://gitter.im/allure-framework/allure-core |
Here is my pom.xml file.
Still It is getting created in target directory. Can you please help me . |
There is at least few problems with your configuration.
BTW what is the point of using Allure 1 ? I recommend you to upgrade to Allure 2, here you can find working example https://github.com/allure-examples/allure-testng-example |
I have updated Pom but still same.
|
Hi, @sgupta3112
Second way is:
|
@eroshenkoam , I have done some changes but Now I am not able to create allure report on given path. Can you please check this pom. Thanks, |
why are you generate report into resource directory?
|
I am trying to run my test on aws device farm and device farm doesn't support target directory. So I need to create allure report in resource directory. |
I have removed that line but still same. allure-result is not getting created at given path. I am trying to do since last 20 hours but no luck. |
Thanks all for help :) |
@sgupta3112 Did you solve your problem? |
Hi guys, this seems a blocker problem, is there any solution for it? Not sure why the ticket is closed as the solution is not found. Allure 2 is trying to create the allure.results.directory directory which in AWS is not allowed because of limited permissions and environment specific structure. Here is the error reported by AWS:
Please note the "allure.results.directory" was not specified. The specific part of the AWS environment is we don't know the path to the execution workspace, it is a random path so it can't be set initially in the allure.properties. Any ideas how to avoid this error? Please note, those options are tried without any luck
Also, please note the java knows where the workspace path is through an environment variable, but how to tell the Allure that? Maybe there is a way to completely disable the Allure if its execution is not needed for a specific environment like AWS? Please advise what to do. |
Try with |
You point to '/allure-results' - it's not right place for allure results. |
@eroshenkoam we are not resolving properties in values, so UPD: I mean for |
Thanks, guys, At this point, the issue still remains actual. |
@sgupta3112 @baev @eroshenkoam @uterator - Is it resolved? For example : |
I am running my test on AWS and there target directory doesn't create.
So I want to create allure-report outside the target,
is there any way to do ?
The text was updated successfully, but these errors were encountered: