feature: delete old packs after serialization#14661
Open
vankop wants to merge 1 commit into
Open
Conversation
Contributor
|
For maintainers only:
|
vankop
commented
Nov 5, 2021
a014734 to
8e04dda
Compare
Contributor
|
Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon. |
60c5e2c to
486b9a8
Compare
|
Any plan to merge this? |
Member
|
@hardikpatel043 near future |
|
Hi Team, This would benefit the world greatly and avoid burning SSD faster... |
|
The webpack cache is unusable on the CI right now if the cache keeps growing for every build. Is the near future approaching? |
|
Could you help with any planned timelines for this fix to be shipped ? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
feature: delete old packs after serialization
closes #13291
Did you add tests for your changes?
not yet
Does this PR introduce a breaking change?
no
What needs to be documented once your changes are merged?
nothing