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
Currently artifacts (reports and products) are stored forever. However, since disk space is limited and some frameworks produce rather large artifacts, it is possible to run out of disk space. An automated process could be made which cleans up old artifacts when they are no longer useful.
There would be two components to such a cleanup system:
a way to configure the clean-up policy: for how long are certain artifacts kept?
the actual cleanup: when an artifact has been flagged for removal, it should be removed from its storage pool
The text was updated successfully, but these errors were encountered:
I created issues in the GitHub tracker for the ideas in this document
that were still relevant: #9#10#11#12#13#14#15#16#17#18#19#20
We want to create a new roadmap at some point, containing visions for
the future rather than concrete feature plans. But when we do that,
it should not be part of the installed documentation, but kept on
for example a web site or wiki instead.
Currently artifacts (reports and products) are stored forever. However, since disk space is limited and some frameworks produce rather large artifacts, it is possible to run out of disk space. An automated process could be made which cleans up old artifacts when they are no longer useful.
There would be two components to such a cleanup system:
The text was updated successfully, but these errors were encountered: