Reduce the number of releases kept on application servers#132
Merged
Conversation
bshand
force-pushed
the
feature/keep_3_releases
branch
from
35a4f1d to
e5beed1
Compare
ollietulloch
approved these changes
Apr 30, 2024
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
3 participants
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.
Reduce the default number of releases we keep on webapp servers to 3 (previously 5).
This does not change the number of releases we keep on daemon servers (default 5 unless overridden): we have much longer lived processes there, and I think there's more risk there of removing the filesystem under running code, e.g. when we have batch tasks that run for many hours and we do a number of beta redeployments on the same day.
This should help a little with our storage issues on various webapp servers.