-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide coverage report format Jenkins can consume #403
Comments
Any updates on whether this issue will be implemented? If not, @mmanela, can you give us any hints on how to implement it? |
I have not looked at it but it should not bee hard to do. Chutzpah has a bunch of transformers (https://github.com/mmanela/chutzpah/tree/master/Chutzpah/Transformers) and one just has to be written for a format that Jenkins would like. Are you interested in helping? |
Yes :) I have never made a big contribution to open source software though,
|
@miparnisari That is exciting. I welcome you to the world of open source software contributions |
Fixed with the emma xml contirbution |
Thank you @miparnisari and @mmanela. |
This is a request to add a code coverage output format that Jenkins can consume. I cannot find a way to integrate Chutzpah's lcov output with Jenkins. It should be possible to integrate Chutzpah's HTML output vis the HTML Publisher plugin, but with the right output I could leverage a plugin to create reports with drill down and links to source files. Here is what my research has turned up:
I hope you will consider adding support for one of these to Chutzpah to make it easier to integrate with Jenkins and other tools.
The text was updated successfully, but these errors were encountered: