Maybe you already solved this. Here is what I found after having the same 
problem:

It started after upgrading a slave machine to Ubuntu 18.04. In the log for 
the slave machine in Jenkins UI I found this error message: 
"java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException". The problem 
seems to be caused by changes to JAXB APIs in newer Java version. Read more 
about this here [1].

My current solution is to change Java version to 8. This is the version 
currently recommended by Jenkins [2]. First I listed my Java versions by 
running this command: "update-java-alternatives --list". Then I selected 
Java 8 by running "update-java-alternatives --set 
/usr/lib/jvm/java-1.8.0-openjdk-amd64". Then I restarted the slave agent 
from the Jenkins UI. Now my cppcheck job went back to normal again.

[1] 
https://stackoverflow.com/questions/43574426/how-to-resolve-java-lang-noclassdeffounderror-javax-xml-bind-jaxbexception-in-j
[2] https://jenkins.io/doc/administration/requirements/java/


Regards,
Tore Havsø Sæstad

On Thursday, September 20, 2018 at 2:29:39 PM UTC+2, fabian wrote:
>
> Hi 
>
> I have a job that among other things uses cppcheck to examine the code. 
> This has worked on several systems (Ubuntu, Debian, Windows). However 
> I have a problem using the same job on the last Ubuntu 18.04. Here's a 
> snippet from a working build: 
>
> (Ubuntu 16.04, CppCheck 1.72) 
> [Cppcheck] Starting the cppcheck analysis. 
> [Cppcheck] Processing 1 files with the pattern 'cppcheck.xml'. 
> [Cppcheck] Not changing build status, since no threshold has been 
> exceeded. 
> [Cppcheck] Ending the cppcheck analysis. 
>
> And this is what happens on Ubuntu 18.04 
>
> (Ubuntu 18.04, CppCheck 1.82) 
> [Cppcheck] Starting the cppcheck analysis. 
> [Cppcheck] Processing 1 files with the pattern 'cppcheck.xml'. 
> [Cppcheck] Error on cppcheck analysis: java.io.IOException: remote file 
> operation failed: 
> /var/lib/jenkins/workspace/inos_unittest_desktop/INOSTYPE/600205020 
> Linux/OPT/Debug/OS/linux/label/inos_desktop at 
> hudson.remoting.Channel@282557ba:Ub18-04-64: java.io.IOException: Remote 
> call on Ub18-04-64 failed 
> Build step 'Publish Cppcheck results' changed build result to FAILURE 
> Build step 'Publish Cppcheck results' marked build as failure 
>
> The cppcheck logfile looks the same, xml with version 2. So what else 
> could be the reason for this exception? Is there a log file on the slave 
> that has more information? Or can I tell the slave to output more 
> information 
> to the master? 
>
> Thanks 
>
> bye  Fabi 
>
>

-- 
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/8061f145-faaa-457e-8bfb-bd4260baee44%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to