-
Notifications
You must be signed in to change notification settings - Fork 176
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
Optimization of storage #126
Comments
Thank you @VojKozel. This will be the next improvement. |
@fescobar when will this be implemented ? |
@AdamRussak don't use CHECK_RESULTS_EVERY_SECONDS:3 for multiprojects. That is going to generate thousands reports. Use CHECK_RESULTS_EVERY_SECONDS: NONE instead. Use the GET /generate-report endpoint once you have all the results files generated. On that way, only you will generate just one report on demand. |
@VojKozel @AdamRussak you will have news soon. |
@VojKozel @AdamRussak The documentation about that is here: Thank you for your suggestions |
@fescobar appreciate it! |
Current solution wasting too much disk storage because of copy-pasting all content via
cp --recursive --preserve=timestamps $PROJECT_LATEST_REPORT/* $NEW_REPORT_DIRECTORY/
For default allure server configurations, files like app.js, styles.css etc.. are absolutely the same and for each report, they take about 2-3MB+. From the perspective where we want to use this server for some automated test which runs multiple times per day, it can waste a lot of storage for no reason.
There should be added some experimental feature (Idk how about all allure server configuration, where these files should be different, but for default allure report from cucumber test it's ok) where it will replace copy-pasting of all files by creating symlinks.
I mean something like
ln -s $PROJECT_LATEST_REPORT/styles.css $NEW_REPORT_DIRECTORY/styles.css
ln -s $PROJECT_LATEST_REPORT/app.js $NEW_REPORT_DIRECTORY/app.js
It will be great if you will think about this feature, it should helpful everyone who wants to use your image for real usage.
The text was updated successfully, but these errors were encountered: