Ah, I see. So you really want Capistrano to just make a "best effort" at performing your commands, and then just report back and say that it failed on these hosts.
Yeah, I can see that now. I'd entertain a patch for that, though I would want the current behavior to remain the default. Perhaps we could just add an option to tasks, indicating that they were "best effort" tasks? task :foo, :best_effort => true do end Or is this an all-or-nothing thing in your case, where every task ought to be best_effort? - Jamis On Jun 7, 2007, at 9:29 AM, Rob Holland wrote: > > On 6/7/07, Jamis Buck <[EMAIL PROTECTED]> wrote: > >> Ah, yes, that does make more sense. What kind of tasks are you >> running, where you want them to continue even if a command fails on >> one server? I'm curious what uses people are putting Capistrano to, >> besides those that I designed it for. > > We're using it to manage some daemons. For things like mass > starting/stopping/configuring of the daemons it's not an all or > nothing thing, we want as many to complete as possible. We are > presuming that erros will need human intervention and will be fixed > case by case. It's different to the case with say, rails, where you > wish everything to be uniform, this is a collection of standalone > machines, as it were. > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
