[Buildbot-devel] Logging html pages per build

[John Pye]

Hey Daniel

I tried to do this a while ago with 'lcov' --
http://ltp.sourceforge.net/coverage/lcov.php -- but didn't have any
success (due to something about the way 'gcov' works). If you (or anyone
else) managed to work out a way of doing the coverage reporting but with
gcov or another GCC-related tool for compiled languages, I'd be very
interested.

In the general case, it would be nice if there were a mechanism for
getting this set of HTML pages back from the buildslave to the buildbot,
so that any buildslave (not just localhost) can make this kind of
reporting. I vaguely remember hearing someone on the list talking about
such a mechanism but not sure.

Cheers
JP

Daniel Benamy wrote:

>Yay for replying to myself.
>
>On Tuesday 27 June 2006 10:53, Daniel Benamy wrote:
>  
>
>>I'm integrating a code coverage tool with a buildbot setup. I've got a step
>>which runs trace2html which spews out some web pages. Right now they just
>>go to a directory served by apache, but I'd like to have the output from
>>each build saved with that build. I think I could hack that on if I knew
>>the build number in my custom buildstep. I'd just create a directory in the
>>apache served area with that number and add a link to it manually. So, does
>>anyone know how to get to the build number? Or is there a better way to do
>>what I want?
>>    
>>
>
>I figured out how to get to the build number. Sorry for the noise about that. 
>But I'd still welcome less hackish ideas for how to solve the bigger problem.
>Dan
>
>
>  
>
-- 
John Pye
University of New South Wales, Sydney, Australia
http://pye.dyndns.org