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
On mar. 5 sept. 2017 à 10:38 Chris B <secondbas...@gmail.com> wrote: > 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 > > Am Mittwoch, 30. August 2017 21:47:36 UTC+2 schrieb 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 >> >> Le lun. 28 août 2017 à 23:29, <pg.sm...@gmail.com> a écrit : >> > 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: >>> >>>> 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-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 >>> <https://groups.google.com/d/msgid/jenkinsci-users/8d148b28-dd7e-4e19-b2c1-45b0e0b33776%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > 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/b8decf52-4792-4f3c-bdfc-131ca5f4e1b8%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/b8decf52-4792-4f3c-bdfc-131ca5f4e1b8%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAPc4eF-tYGquJu5Mey_dJAyPD%2BTWpsLJNU9dsG3L01%3DjsoR-PA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
