[Buildbot-devel] Pipe ShellCommand output to file on Windows

[Thomas Middeldorp]

I'm pretty sure this works if you use a string for the command instead 
of a list (e.g. command="xt-size.exe libWhatever.a --totals > 
memstats.txt") however you quickly run into other problems when doing 
this on Windows, like as soon as you have a parameter containing a space 
etc. Not sure exactly what Buildbot does differently in each of these 
cases though.

- Thomas


On 23/06/2014 3:43 a.m., Dustin J. Mitchell wrote:
> On Mon, Jun 16, 2014 at 3:54 PM, Alex Escott <AE at malaspina-labs.com> wrote:
>> As the title says... I have a ShellCommand step like this:
>>
>> Steps.append(ShellCommand(command=['xt-size.exe','libWhatever.a','--totals','>','memstats.txt']))
>>
>> When I run it, it gives an error:
>> xt-size.exe: Warning: '>' is not an ordinary file
>> xt-size.exe: 'memstats.txt': No such file
>>
>> I can run the command from the command line manually, that works. I've also tried a single string (.exe and args in one string) as the command parameter, still the same error.
>
> I'm surprised this didn't help, actually.  Given a string, Buildbot
> prefixes it with 'CMD.EXE /c', then puts the whole thing in a
> temporary batch file and executes it.  So I'd expect a batch file
> containing
>
> CMD.EXE /c xt-size.exe libWhatever.a --totals > memstats.txt
>
> which is exactly what Vasily suggested.  I don't understand why that
> wouldn't work..
>
> Dustin
>
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>