I can't comment on the pipelines, but the Emma Coverage Plugin is something 
we rarely use and the "bad looking picture" as you describe it shows up in 
every of our builds and it's, well you said it, just ugly to look at and 
conveys something is broken even though it isn't.

So I am highly in favor of removing that hard dependency so everyone can 
decide for themselves if they want coverage reports or not.

On Thursday, 24 August 2017 20:59:35 UTC+2, Ivo Bellin Salarin wrote:
>
> Hello everyone,
>
> I have implemented a couple of blueprints (i.e. modification requests) of 
> the MSTest plugin for Jenkins. Since I haven't any other way to contact my 
> users, I will try to use this mailing list to describe the changes and have 
> your opinion.
>
> First, the possibility to use the MSTest plugin in a pipeline 
> (jenkinsfile). The users will be able to call the plugin using the 'mstest' 
> symbol.
>
> Second. Because of the changes apported to implement the pipeline, and 
> because of several users request, I have dropped the dependency upon the 
> Emma plugin. Versions 0.12 through 0.19 were showing coverage trends (or a 
> bad looking picture if the tests weren't computing any coverage). These 
> versions were 1) discovering code coverage reports linked by the test 
> report 2) converting it to the Emma format 3) adding a Emma report to the 
> build.
> Starting from the 0.20 version, the plugin will perform the steps 1 and 2, 
> but it won't do the step 3. In order to show the coverage report/trends, 
> you will have to add the Emma plugin (or the jacoco plugin) and tell it to 
> find for the reports whose name matches '**/emma/coverage.xml'.
>
> Dear users, what do you think about these changes? I will wait 2 weeks 
> before releasing the 0.20 version.
>
> BTW, someone has tested the 0.20 version, but only partially. I have 
> executed all the unit tests in my possession (and I have written some more 
> for the occasion). But the number of TRX/coverage reports in my possession 
> is very limited. So, if anybody can help testing the 0.20 version, please 
> send me a private message.
>
> Many thanks for your attention,
> Have a great day,
> Ivo
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a42ae13a-590a-444b-aead-7da62c75c9fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to