Re: Scheduling lcov code coverage script

On Wed, Dec 10, 2014 at 4:51 PM, Norbert Thiebaud <nthiebaud@gmail.com>
wrote:
> On Wed, Dec 10, 2014 at 9:45 AM, Maarten Hoes <hoes.maarten@gmail.com>
wrote:
> > If still interested (and my tests completes as expected), I could
submit the
> > contents of my .tb directory somewhere, but im not too sure if that's
still
> > needed or relevant anymore with your current modifications/version of
the
> > script:
>
> I'm not using tb. I did the modification to be able to run the lcov
> script stand alone triggerred by jenkins.
Aawwwhhh... Now *I* wanted to do that task (with the required hand holding,
of course ;)


> 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 ?

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 lcov-reports.sh script).


> Let me emphasis: I made some modification/extenstion to fit better my
> use case.. that does not imply that the model you used was wrong or
> needed change
I guess it's just that I dont see the 'tinderbox use cases' as clearly as
you anymore, especially when now youve already got code coverage working in
the Jenkins case.



- Maarten