Thanks Jeff. As Fabric runs a given task in parallel, what would be the best way to collect information from various runs on different hosts, and publish it once task finishes?
On Wed, May 29, 2013 at 1:32 PM, Jeff Forcier <[email protected]> wrote: > If you check the API docs you'll see that `execute()` returns a > host-string-keyed dict whose values are the return code of each > iteration of the task, or an exception object if the task failed > partway. That should get you at least part of the way there. Either > way, summary reporting (in any mode, serial or parallel) is something > that's definitely on the table at some point. > > On Wed, May 29, 2013 at 1:04 PM, Vineet Gupta <[email protected]> wrote: > > I am trying to find best option to summarize results from parallel > execution > > of certain task. Usually what happens that I have to look through the > debug > > trace to figure out what succeeded and what failed. What I'd like to do > is > > an option to look into result.return_code and construct a result in a > > tabular structure with hosts which "passed" and hosts which didn't pass. > > > > Thanks, > > Vineet > > > > _______________________________________________ > > Fab-user mailing list > > [email protected] > > https://lists.nongnu.org/mailman/listinfo/fab-user > > > > > > -- > Jeff Forcier > Unix sysadmin; Python/Ruby engineer > http://bitprophet.org >
_______________________________________________ Fab-user mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/fab-user
