Fwd: timing report

5 views
Skip to first unread message

Eric Hexter

unread,
Sep 10, 2009, 9:44:45 AM9/10/09
to psak...@googlegroups.com
Moving this thread from the users list to dev.
 
I can see making the timing report show up as xml  I hacked that together...
 
The easiest way to produce xml for the entire run is piping the command to a format or exportcli-xml ie
psake.ps1 | formatcli-xml results.xml  
 I would say that is just too much work to put on the end users of the system.
 
My next idea is to pipe the Run-Psake function to an output.  I think that this will require piping every call inside of a script to some sort of wrapping / logging function that would store the output and write it to the console.  I will spike this as I get time.
 
Anyone else have some ideas to implementation?
 
---------- Forwarded message ----------
From: James Kovacs <jko...@post.harvard.edu>
Date: Wed, Sep 9, 2009 at 11:45 PM
Subject: Re: timing report
 
 
I think -xml would be preferable and then output everything in XML. Not sure how hard this would be.
 
As for being a PowerShell n00b, join the club. I created psake to sharpen my PowerShell skills. :)
 
BTW - We should take this over to the psake-dev mailing list.
 
James
--
James Kovacs, B.Sc., M.Sc., MCSD, MCT
Microsoft MVP - Solutions Architect
403-397-3177 (mobile)
 
 
On Fri, Sep 4, 2009 at 2:36 PM, Eric Hexter <eric....@gmail.com> wrote:
>
> James,
>  
> If you want to give some direction of how you would want to specify creating an xml timing report. like the one which is derived from nant xml output for use inside of a CI server I would be willing to send a patch.  Do you have any thoughts for it.?
>  
> I am not sure if it makes sense to add a -xml flag or say a -timingxml   . I am a total PowerShell n00b so please enlighten me.
>  
>  
> Thanks,
> Eric
>  
>  
> Eric Hexter
>
> Principal Consultant | Headspring Systems | www.HeadspringSystems.com
> email | ehe...@HeadspringSystems.com
>
>
>
>
 
 
 
 
 
Reply all
Reply to author
Forward
0 new messages