[almighty] Coverage service. How to proceed?

[Konrad Kleine]

Hi all,

I've been investigating two coverage services on the web:

https://codecov.io/gh/almighty/almighty-core/pull/235 and
https://coveralls.io/github/almighty/almighty-core.

The reason was to have some publicly facing coverage information for
almighty-core (and possibly other repos under the almighty umbrella).

The pull requests to integrate codecov.io can be found here (
https://github.com/almighty/almighty-core/pull/235) and this is how it
looks in the PR once coverage was uploaded:


​

The pull requests to integrate coveralls.io can be found here (
https://github.com/almighty/almighty-core/pull/238) and this is how it
looks in the PR once coverage was uploaded:


​
While all of this is fine and dandy, I don't very much like the way these
services collect coverage information. Codecov.io collects all *coverage*
files which is simply wrong in our case and I don't want to adapt to this
system. We have very good reasons to have many coverage files (e.g. for
different coverage modes and to not recollect coverage information every
time).
Also, both service require a token to be submitted with the request made to
the service. Currently this is hard-coded in the PRs that I wrote just to
see some results. Those would have to be made invisible for others which
can become pretty hard in the current jenkins slave -> worker setup. Even
if the token is stored in environment variable it is easy to figure out by
simply modifying the cico_run_tests.sh script.

I don't see much benefit from having such a coverage service and I'd like
to see the Jenkins cobertura plugin in action (hopefully after the next
maintenance window). Then we don't have to mess with any external service
or token. I bet the devtools-test team has some ideas around providing code
coverage for the public.

Please, let me know what to do with those PRs 235 and 238.

Regards,
Konrad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20160909/b3ffa939/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2016-09-09 18-25-58.png
Type: image/png
Size: 57852 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20160909/b3ffa939/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2016-09-09 18-25-38.png
Type: image/png
Size: 38188 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20160909/b3ffa939/attachment-0001.png>