[//]: # (
. Note: for support questions, please use Stackoverflow or Gitter.
. This repository's issues are reserved for feature requests and bug reports.
.
. In case of any problems with Allure Jenkins plugin please use the following repository
. to create an issue: https://github.com/jenkinsci/allure-plugin/issues
.
. Make sure you have a clear name for your issue. The name should start with a capital
. letter and no dot is required in the end of the sentence. An example of good issue names:
.
. - The report is broken in IE11
. - Add an ability to disable default plugins
. - Support emoji in test descriptions
)
I'm submitting a ...
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support request here, see note at the top of this template.
What is the current behavior?
I am working on generating allure reports with Marathon library for my Espresso automation test to embedd screenshots in the report. The test reports were generating fine with screenshots for below configuration
Allure-gradle @2.8.1
Marathon-gradle plugin @0.6.2
Gradle 6.0
Since we migrated to Gradle 7.0 and we had open issues of multiple getters with allure-gradle version 2.8.1, so I upgraded allure-gradle version from 2.8.1 to 2.9.4 but I was not able to make this reports generate with current configuration. When tried with running it with warning mode - ./gradlew allureReport --warning-mode=all
I am getting below error:
Resolution of the configuration :allureRawResultDirs was attempted from a context different than the project context. Have a look at the documentation to understand why this is a problem and how it can be resolved. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. See
allure-results are generating under marathon reports but allure reports are not getting generated
What is the expected behavior?
Allure reports should generate under app/build/reports/allure-report
[//]: # (
. e.g. detailed explanation, stacktraces, related issues, suggestions
. how to fix, links for us to have more context, eg. Stackoverflow, Gitter etc
)
[//]: # ( . Note: for support questions, please use Stackoverflow or Gitter. . This repository's issues are reserved for feature requests and bug reports. . . In case of any problems with Allure Jenkins plugin please use the following repository . to create an issue: https://github.com/jenkinsci/allure-plugin/issues . . Make sure you have a clear name for your issue. The name should start with a capital . letter and no dot is required in the end of the sentence. An example of good issue names: . . - The report is broken in IE11 . - Add an ability to disable default plugins . - Support emoji in test descriptions )
I'm submitting a ...
What is the current behavior?
I am working on generating allure reports with Marathon library for my Espresso automation test to embedd screenshots in the report. The test reports were generating fine with screenshots for below configuration Allure-gradle @2.8.1 Marathon-gradle plugin @0.6.2 Gradle 6.0
Since we migrated to Gradle 7.0 and we had open issues of multiple getters with allure-gradle version 2.8.1, so I upgraded allure-gradle version from 2.8.1 to 2.9.4 but I was not able to make this reports generate with current configuration. When tried with running it with warning mode - ./gradlew allureReport --warning-mode=all I am getting below error:
Resolution of the configuration :allureRawResultDirs was attempted from a context different than the project context. Have a look at the documentation to understand why this is a problem and how it can be resolved. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. See
allure-results are generating under marathon reports but allure reports are not getting generated
What is the expected behavior?
Allure reports should generate under app/build/reports/allure-report
Please tell us about your environment:
allure { report { version.set("2.13.9") reportDir.file(project.rootDir.absolutePath+"/app/build/reports/allure-report") } }
Other information
[//]: # ( . e.g. detailed explanation, stacktraces, related issues, suggestions . how to fix, links for us to have more context, eg. Stackoverflow, Gitter etc )