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 the release_roles
EDIT: FTR, set :rvm1_roles, [:app] does work for my needs but it would be nice to respect no_release
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: trueThis attribute looks like it was restored to Capistrano 3 and a
release_rolesaccessor 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_rolesEDIT: FTR,
set :rvm1_roles, [:app]does work for my needs but it would be nice to respectno_release