Bunch of tasks to achieve more controlled deploys #60
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
|
Please copy the pull request description text into the commit message, so it will be visible in the git history. Also, is there any chance you could make this description a bit more verbose and explicit? It sounds good, but I'm not a unicorn expert so I'm having trouble fully understanding it. Thanks! |
Don't send winch to a unicorn that's not running
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.
Using WINCH to shut down down old workers after some time, without killing the master in case we want to use it again(which will be achieved by sending HUP to it and making it spawn more workers).
When we're sure that everything we can use the stop_old_master task, or do the forementioned fallback