Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


Hi,


There's has been done some work recently to create a small bash shell
script to automate the creation of lcov code coverage reports of arbitrary
tests run on the libreoffice code. It can be found at
'buildbot.git/lcov-report/lcov-report.sh' [1], and it's accompanied with a
small README [2] on it's usage. I ran a few tests with it, and cannot find
any more bugs in it, so I guess it's time to see if we can start using it,
and start scheduling it somehow and upload the reports someplace.

To allow for all kinds of different tests to be run, the script itself runs
no tests: Instead, you can easily insert obvious candidates like 'make
check' or any other tests in the pipeline, and generate a report on that.

Ive heard some talk about using/integrating it with Jenkins (?) now, to
take care of the scheduling of it, updating (git clone/pull) libreoffice
sources, and uploading the reports somewhere. I have no experience with
Jenkins myself, but am willing to learn. If a simpler scheduling mechanism
like cron is used, some more code to clone/pull sources and upload reports
needs to be added to the script.

Where to go from here ?


Regards,


Maarten Hoes



[1]
https://gerrit.libreoffice.org/gitweb?p=buildbot.git;a=blob;f=lcov-report/lcov-report.sh;hb=HEAD

[2]
https://gerrit.libreoffice.org/gitweb?p=buildbot.git;a=blob;f=lcov-report/README;hb=HEAD

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.