Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd cache busting to generated HTML report #1111
Open
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currenlty the HTML report requests the json files with paths such as
widgets/history-trend.json. Some web servers which host Allure reports will cache these data files or have the browser cache them (based on response headers). Because of this outdated data will be shown.My specific case for this is hosting the Allure results on GitLab. As part of a CI/CD pipeline I publish the test results to GitLab pages. This way you can always see the latest test results for the master branch. However because of above issue, and since you cannot modify the caching headers for GitLab pages, you end up with outdated test results being shown.
Describe the solution you'd like
Implement a Cache Busting mechanism in the Allure HTML report generation. All three mechanisms would work:
The 'version' could be a random string, that is generated once for every report, and used in all names / paths / query strings.
Describe alternatives you've considered
Fixing the issue server side. There are two issues with that: