Skip to content
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

Closed
VojKozel opened this issue Sep 7, 2020 · 6 comments
Closed

Optimization of storage #126

VojKozel opened this issue Sep 7, 2020 · 6 comments
Labels
enhancement Enhancement released Released

Comments

@VojKozel
Copy link

VojKozel commented Sep 7, 2020

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.

@fescobar fescobar added the backlog Backlog label Sep 7, 2020
@fescobar
Copy link
Owner

fescobar commented Sep 7, 2020

Thank you @VojKozel. This will be the next improvement.

@fescobar fescobar added the enhancement Enhancement label Sep 14, 2020
@AdamRussak
Copy link

@fescobar when will this be implemented ?
we are using the image and our storage is getting full with only 40 tests (150GB)

@fescobar
Copy link
Owner

fescobar commented Dec 1, 2020

@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.
I will continue developing the next year.

@fescobar fescobar added work in progress Work in progress and removed backlog Backlog labels Dec 25, 2020
@fescobar
Copy link
Owner

@VojKozel @AdamRussak you will have news soon.

@fescobar fescobar added testing Testing and removed work in progress Work in progress labels Dec 26, 2020
fescobar added a commit that referenced this issue Dec 26, 2020
fescobar added a commit that referenced this issue Dec 26, 2020
fescobar added a commit that referenced this issue Dec 28, 2020
@fescobar fescobar added ready to be released Ready to be released and removed testing Testing labels Dec 28, 2020
@fescobar
Copy link
Owner

fescobar commented Dec 28, 2020

@VojKozel @AdamRussak
The version 2.13.7 was released with the improvement suggested as EXPERIMENTAL FEATURE
https://github.com/fescobar/allure-docker-service/releases/tag/v2.13.7

The documentation about that is here:
https://github.com/fescobar/allure-docker-service#optimize-storage

Thank you for your suggestions

@fescobar fescobar added released Released and removed ready to be released Ready to be released labels Dec 28, 2020
@AdamRussak
Copy link

@fescobar appreciate it!
Updated and checking!

@fescobar fescobar closed this as completed Jan 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement released Released
Projects
None yet
Development

No branches or pull requests

3 participants