|
Re: not aborting on command failure - batching hosts: msg#00157lang.ruby.capistrano.general
On 20 Dec, 19:50, Jamis Buck <ja...-uHoyYlH2B+GakBO8gow8eQ@xxxxxxxxxxxxxxxx> wrote: > Yes, you can do: > > task :foo, :roles => %w(whatever), :on_error => :continue do > run "something that might fail" > end > > The :on_error => :continue bit tells capistrano to continue on to the > next task, even if the command fails for any of the servers. > > As for running commands on N hosts at a time, that's what Capistrano > is all about. Just describe the hosts in roles, and then specify those > roles in the :roles parameter when defining the task. Or, you can use > the :hosts parameter and just give it an array of servers directly. > > - Jamis jamis, Thanks! I wasn't totally clear about the second question. Say I have 400 hosts, and I only want to run something on 5 at a time, instead of all of them. Can I restrict to operating in batches? A good use case example is a set of web servers that have dependencies on each others deploys and need to having 'rolling' deploys. While I know this could be done by placing them in different roles, it wouldd be tedious to do it with all 400 if all I really want is to batch the execution. Josh |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Hi to all: 00157, jacintabailey-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx |
|---|---|
| Next by Date: | Re: not aborting on command failure - batching hosts: 00157, Mislav Marohnić |
| Previous by Thread: | Re: not aborting on command failure - batching hostsi: 00157, Jamis Buck |
| Next by Thread: | Re: not aborting on command failure - batching hosts: 00157, Mislav Marohnić |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |