-
Bug
-
Resolution: Fixed
-
Major
Testlink configuration:
Jenkins configuration:
Jenkins job FAILS:
08:23:20 Looking for the test results of TestLink test cases. 08:23:20 08:23:20 Looking for test results in JUnit classes. 08:23:20 08:23:21 FATAL: null 08:23:21 java.lang.NullPointerException 08:23:21 at hudson.plugins.testlink.result.JUnitCaseClassNameResultSeeker.getJUnitNotes(JUnitCaseClassNameResultSeeker.java:138) 08:23:21 at hudson.plugins.testlink.result.JUnitCaseClassNameResultSeeker.seek(JUnitCaseClassNameResultSeeker.java:99) 08:23:21 at hudson.plugins.testlink.TestLinkBuilder.perform(TestLinkBuilder.java:159) 08:23:21 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) 08:23:21 at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703) 08:23:21 at hudson.model.Build$RunnerImpl.build(Build.java:178) 08:23:21 at hudson.model.Build$RunnerImpl.doRun(Build.java:139) 08:23:21 at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:473) 08:23:21 at hudson.model.Run.run(Run.java:1408) 08:23:21 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 08:23:21 at hudson.model.ResourceController.execute(ResourceController.java:88) 08:23:21 at hudson.model.Executor.run(Executor.java:238)
Full console out can be found full-log.txt
Also JUnit report is attached - TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml
[JENKINS-13150] 'FATAL: null' while looking for test results in JUnit classes
Jaroslavas D.
added a comment - Plug-in version is 3.1. So, it should be fixed in 3.1.1.
I have requested plugin' update.. and if I'll be lucky it'll happen in the end of this week 
Then I'll comment here.
P.S. Could you please delete attachments: full-log.txt and TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml. I found some information that shouldn't be public.
Thank You!
Jaroslavas D.
added a comment - Plug-in version is 3.1. So, it should be fixed in 3.1.1.
I have requested plugin' update.. and if I'll be lucky it'll happen in the end of this week Then I'll comment here.
P.S. Could you please delete attachments: full-log.txt and TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml . I found some information that shouldn't be public.
Thank You!
Cool, will wait for your comment here then many thanks.
I've dropped a message at #jenkins IRC channel asking for someone with admin rights to remove it. I don't have this rights, sorry 
Hi Bruno.
Still have problems with new plugin version...
If no seek strategy is defined - job configuration can be saved
BUT
If some seek strategy is defined - exception is thrown on save logg.txt
Jaroslavas D.
added a comment - - edited Hi Bruno.
Still have problems with new plugin version...
If no seek strategy is defined - job configuration can be saved
BUT
If some seek strategy is defined - exception is thrown on save logg.txt
Hi Jaroslavas,
I believe this was caused due to the increment of new fields for the strategies (probably attachment and/or notes checkbox).
My XStream-fu is quite rusty =( sorry for not taking care for backward compatibility. Would it be too troublesome for you create a new job with the same configuration and see if that works, please?
Sorry again,
Bruno
Jaroslavas D.
added a comment - Hi, Bruno.
Everything works fine with new job! Thank You.
I think ticket can be closed
Jaroslavas D.
added a comment - Hi, Bruno.
Everything works fine with new job! Thank You.
I think ticket can be closed Jaroslavas D.
added a comment - Bruno, please, one more time ask someone to delete attachments: full-log.txt and TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml
Thank You!
Jaroslavas D.
added a comment - Bruno, please, one more time ask someone to delete attachments: full-log.txt and TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml
Thank You! Thanks for reporting Jaroslavas!
I will read more about XStream to see ways to maintain the backward compatibility in new version (though I'm aware sometimes it's not possible
Have a good day!
I asked to remove the attachments again on IRC hopefully someone with admin karma will remove them. Sorry.
Jaroslavas D.
added a comment - Everything works just fine now!
Thank You for your work! 
The only way that I know is by having a look at the plug-ins configuration screen. Maybe someone with admin access could tell which version you're using? I know there was a fixed NullPointerException in the same part of the code, but it was fixed in 3.1.1. If you could have a look on it, that would help a lot
I had a look at the code here, and everything seems fine. The changes that I mentioned are related to include more details, like which method passed and which failed, in the test execution notes.
Sorry for not being able to help you finding the plug-in version. We could add the plug-in version in the console too in future versions, but that could cause problems if someone (specially dumb me
forgot to update the text displayed in the console.
Bruno