Scheduling lcov code coverage script

Norbert Thiebaud nthiebaud at
Wed Dec 10 08:27:51 PST 2014

On Wed, Dec 10, 2014 at 10:10 AM, Maarten Hoes <hoes.maarten at> wrote:
>> But that is a special case... making this available under tb is still
>> a valuable thing to make it easier for people running such tb-box to
>> include code coverage in the mix.
> Now Im confused. Why would you want to run the same code coverage on a tb,
> when those results are already provided by a Jenkins build ? Doesnt it make
> more sense to 'just' have one box that (in this case, triggered by Jenkins),
> takes care of all your code coverage needs ?

because someone may want to work on improving the coverage.. it could
be usefull for someone to have his own tb box to do coverage report
on a feature branch or even a local one....

maybe someone will want to run some test coverage that are not yet
part of the 'canonical one' etc...
in any case it is always good to be flexible, you never know what
vreative way to use a good script one will find :-)

> Anyway, I guess I could, once I verified that it works as intended, put the
> contents of my .tb directory in a subdirectory of
> buildbot.git/lcov-report/tinderbox, accompanied with a small README
> explaining how you could go about integrating the two ?


> And the one lacking feature of the current way is of course that the reports
> gets generated, but you still have to take care of the uploading them
> somewhere useful part. (assuming youve done that with Jenkins, and not by
> modifying the script).

I have not addressed it yet.. but that should be not too hard to do with jenkins
I'll just have to coordinate with cloph to find a home for it

More information about the LibreOffice mailing list