Hi,
Why does cap update_current ask for a svn passwd? I scanned the source
(see below) and it seems checkout and update are a little different in
that update doesn't include #{authorization} in the command.
def checkout(actor)
op = configuration[:checkout] || co
command = #{svn} #{op}
Jeroen, that does, indeed, look like a bug.
- Jamis
On Mar 5, 2007, at 5:17 AM, jeroen wrote:
Hi,
Why does cap update_current ask for a svn passwd? I scanned the source
(see below) and it seems checkout and update are a little different in
that update doesn't include #{authorization} in the
cool, and sorry for not attaching a patch, but it seemed kinda overkill :-)
jeroen
Jamis Buck wrote:
Jeroen, that does, indeed, look like a bug.
- Jamis
On Mar 5, 2007, at 5:17 AM, jeroen wrote:
Hi,
Why does cap update_current ask for a svn passwd? I scanned the source
(see below)
I have added a new role (role :new_role, new_role) for some tasks
specific to that box.
Now the :setup (and other) tasks that have no role restrictions, and so
run for all roles, are trying to execute on the new_role box.
What is the simplest approach to having standard tasks NOT execute for
