Re: [Fab-user] Catching errors in local calls

[Jeff Forcier]

Hi David,

On Fri, Sep 24, 2010 at 1:33 AM, David <address@hidden> wrote:

> I am using fabric for some simple test deployment scripts, and I have
> encountered a slightly annoying behavior when local(some_cmd) fails. In that
> case, the output of local is not displayed, making debugging the issue a bit
> difficult.

I'm not sure what your exact code structure is (it's usually helpful
to include at least a small snippet when posting ;)) but if you're not
specifying capture=False, local() captures the output by default,
instead of displaying it:

    
http://docs.fabfile.org/0.9.2/api/core/operations.html#fabric.operations.local

Best,
Jeff

>
> Is there a way to disable abort and catch exception on errors to deal with
> them ? I understand I could use debug printing, but if possible, I would
> like to *always* get that output, but *only* in case of failure.
>
> cheers,
>
> David
>
> _______________________________________________
> Fab-user mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/fab-user
>



-- 
Jeff Forcier
Unix sysadmin; Python/Ruby developer
http://bitprophet.org