Hey,
we recently switched code coverage from codecov to code climate as we
had serious problems with measurements of code based on push-to-master
backend commits. This changes the workflow a bit. I spare you the CI
setup details and concentrate on what you see:
1. Measurement on pull requests
Code climate sets the status of pull-requests according to:
- You are not allowed to decrease overall coverage (the
codeclimate/total-coverage check)
2. Viewing code coverage
To view the code coverage you have to install the code climate
browser extension and navigate to the code in github. See
https://docs.codeclimate.com/docs/browser-extension for details.
There is no way to distinguish between the merged coverage reports
(API vs. webui)...
3. Viewing code coverage trends for files
Code climate has a "log" on how files improved/degraded in code
coverage. See it here:
https://codeclimate.com/github/openSUSE/open-build-service/progress/coverage
Hope that helps to understand what has changed. Happy hacking,
Henne
--
Hendrik Vogelsang, Open Build Service Team
SUSE LINUX GmbH, GF: Felix Imendörffer, HRB 21284 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
--
To unsubscribe, e-mail: obs-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: obs-devel+owner(a)opensuse.org
