You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the 2.24.0 release the support for generating single file reports introduced a bug that completely ignores the environment variable to disable analytics on the generated html report.
Describe the Bug
On the 2.24.0 release the support for generating single file reports introduced a bug that completely ignores the environment variable to disable analytics on the generated html report.
The usage in the template is
allure2/allure-generator/src/main/resources/tpl/index.html.ftl
Lines 28 to 30 in b856621
To the extend of my understanding (rather limited) the configuration is later overwritten by the hard coded values here:
allure2/allure-generator/src/main/java/io/qameta/allure/core/ReportWebGenerator.java
Lines 141 to 148 in 8d41e9d
ignoring the config set by
allure2/allure-generator/src/main/java/io/qameta/allure/core/ReportWebPlugin.java
Line 88 in b856621
allure2/allure-generator/src/main/java/io/qameta/allure/core/ReportWebPlugin.java
Line 91 in b856621
Steps to Reproduce
Generate the report with the env variable
ALLURE_NO_ANALYTICS=true
the generated report will still have analytics.Snapshot from a report:
Expected Behaviour
it does not include the analytics
Screenshots or Additional Context
What Language are you using?
JavaScript, TypeScript
What Framework/Allure Integration you are using?
allure-commandline
What version of Allure Integration you are using?
2.24.0
What version of Allure Report you are using?
2.24.0
Code of Conduct
The text was updated successfully, but these errors were encountered: