Remove more than X old releases in Baremetal deploy #5359
Closed
Conversation
This file contains 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
cannikin
added
topic/deployment
release:feature
This was referenced Apr 29, 2022
# Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
Merged
|
Consolidated in #5500 |
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.
This adds a step at the end of a Baremetal deploy that will remove a number of old releases, keeping a configurable number still on the server (for rollbacks).
This code is branched from #5349 and assumes it will be merged first!
Closes #5298
Release Notes
Baremetal will now cleanup old deploy codebase directories at the end of a deployment! It defaults to keep the last 5 deployments, but this can be configured in
deploy.tomlwith thekeepReleasesoption:[[servers.production]] host = "server.com" username = "ubuntu" agentForward = true sides = ["api", "web"] path = "/var/www/myapp" processNames = ["api"] repo = "git@github.com:myorg/myrepo.git" branch = "main" + keepReleases = 5Why keep around old deploys? In case something goes horribly wrong and you need to rollback!
This config setting is optional and will default to keeping the last 5 deploys if not set.