I'm not sure I follow. Both a failed connection and a failed command cause Capistrano to abort. How is the final result any different? Your post didn't give much in the way of a use case--could you explain a bit more here? I'm curious to know how you're using this.
- Jamis On Jun 7, 2007, at 4:40 AM, tigger wrote: > > > On Jun 5, 4:17 pm, Fredrik <[EMAIL PROTECTED]> wrote: >> Thanks Jamis. I see your points. > > I also see the point, but I disagree. I think a host connection > failure is the same as a command failure, and I'd like to handle them > in the same place. I have written a temporary hack which is listed at: > http://rubyireland.com/2007/5/28/handling-connection-failures-with- > capistrano > > You will probably need to remove the logger.important line for it to > work. > > I've not time right now to write a sensible patch, but I will do so > next week. I'd like this to at least be an option in capistrano. > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
