MSTest plugin poll

[Ivo Bellin Salarin]

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

[florian...@gmail.com]

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.

[Sebastian Stautz]

I appreciate the compatibility to pipeline/jenkinsfile. Would be nice to use it again directly.
I haven't used yet the coverage trends.

[pg.sm...@gmail.com]

The new setup is more flexible and looks fine for me.

Op donderdag 24 augustus 2017 20:59:35 UTC+2 schreef Ivo Bellin Salarin:

[Ivo Bellin Salarin]

An alpha version is available for everyone on the jenkins-ci.org repository. If you're willing to get it, follow the instructions available on:

https://jenkins.io/blog/2013/09/23/experimental-plugins-update-center/

Thanks everybody,

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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/8d148b28-dd7e-4e19-b2c1-45b0e0b33776%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Chris B]

Hi,

there seems to be a problem with the MSTest Plugin in a none-pipeline job:

Results file:  D:\Workspace\PRODUCT\trunk\testresult.trx
Test Settings: Default Test Settings
[MSTEST-PLUGIN] INFO processing test results in file(s) **/*.trx
[MSTEST-PLUGIN] INFO processing report file: D:\Workspace\PRODUCT\trunk\testresult.trx
ERROR: Build step failed with exception
java.lang.NullPointerException
	at hudson.plugins.mstest.FileOperator.safeDelete(FileOperator.java:10)
	at hudson.plugins.mstest.MSTestReportConverter.transform(MSTestReportConverter.java:157)
	at hudson.plugins.mstest.MSTestReportConverter.transform(MSTestReportConverter.java:74)
	at hudson.plugins.mstest.MSTestTransformer.invoke(MSTestTransformer.java:70)
	at hudson.plugins.mstest.MSTestTransformer.invoke(MSTestTransformer.java:23)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2750)
	at hudson.remoting.UserRequest.perform(UserRequest.java:121)
	at hudson.remoting.UserRequest.perform(UserRequest.java:49)
	at hudson.remoting.Request$2.run(Request.java:325)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at hudson.remoting.Engine$1$1.run(Engine.java:69)
	at java.lang.Thread.run(Unknown Source)

Configuration was unchanged after upgrade from 0.19 to 0.20 alpha. 

Chris

[Ivo Bellin Salarin]

Thanks Chris for your bug report,
I'll have a look at this problem tomorrow.
I'll send you an email when a new version is available for test.

Have a great day,
Ivo

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b8decf52-4792-4f3c-bdfc-131ca5f4e1b8%40googlegroups.com.