Use release_roles instead of roles so we only run rsync on nodes we are deploying to #10
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
…re deploying on to
ezekg
pushed a commit
to ezekg/capistrano-rsync
that referenced
this pull request
Jan 4, 2016
git <1.9 needs fetch tags to be done on its own
|
is there a way to set release_roles within command line like we can do with --roles option ? |
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.
Capistrano 3.1.0 is using release_roles do identify servers that we actually want to deploy on to.
This fix ensures we only sync code on to servers that we want to release on to (e.g. where no_release != true)