[Buildbot-devel] Confused about adding a LogObserver

Niklaus Giger niklaus.giger at member.fsf.org
Thu Aug 24 19:07:33 UTC 2006


Thanks a lot to everybody who contributed to this new version. Using a CSS the 
waterfall looks a lot prettier! And I use the WithProperties a lot to pass 
parameters to the waterfall display or custom build scripts.

I was quite excited about the new LogObserver feature in buildbot 0.7.4 as I 
have some outstanding suggestiong to collect the compiler warnings and put 
them into some more attractive (may HTML) form, or at least just present the 
warnings in a separate file.

The NEWS and manual however didn't lead me to a working solution, particulary 
I look at the section "Using LogFiles in custom BuildSteps". Could somebody 
with more insight in the buildbot clarify a little bit?

I would like:
a) have a second logfile which contains only the warnings of a make (running 
GCC) getting some from the normal stdio of the step. So I added the suggested 
createSummary procedure to my master.cfg (A hint where the procedure should go 
would be appreciated). I just changed the if to match "warning" or "Warning".

b) Then (following a suggestion from then NEW file) I added a logFiles = 
{ 'createSummary' : 'stdio' } to my build step. (Why is this not mentioned in 
the manual?)

c) After restarting the buildmaster and a simple build, to my great deception 
the resulting log file was empty? I suppose this is the case, because I did 
not generate (e.g. using tee) a 'stdio' file on the slave. Is there no way to 
feed the stdio to the logObserver?

Any hints would be appreciated.

Thanks in advance

Niklaus Giger

More information about the devel mailing list