We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no_release: true
I have a server that is part of my deployment process but does not need a release, or rvm for that matter, and has been marked with no_release: true
This attribute looks like it was restored to Capistrano 3 and a release_roles accessor was added to limit roles where tasks should be performed:
release_roles
capistrano/capistrano@97d0ddf#diff-0be8aada39197e923b01120ed1917c57R46
I have had problems deploying as the tasks in rvm1 are being run against all roles, not just the release_roles
roles
EDIT: FTR, set :rvm1_roles, [:app] does work for my needs but it would be nice to respect no_release
set :rvm1_roles, [:app]
no_release
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I have a server that is part of my deployment process but does not need a release, or rvm for that matter, and has been marked with
no_release: true
This attribute looks like it was restored to Capistrano 3 and a
release_roles
accessor was added to limit roles where tasks should be performed:capistrano/capistrano@97d0ddf#diff-0be8aada39197e923b01120ed1917c57R46
I have had problems deploying as the tasks in rvm1 are being run against all
roles
, not just therelease_roles
EDIT: FTR,
set :rvm1_roles, [:app]
does work for my needs but it would be nice to respectno_release
The text was updated successfully, but these errors were encountered: