Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-10030

Builds fail in JUnit test archiving (since 1.416) if specifying JDK other than the container

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • core, junit-plugin
    • None
    • Windows Server 2008 R2
      Jetty 7.3.0.v20110203
      Jenkins 1.416

      After update Jenkins from 1.415 to 1.416,
      our maven projects build fail every time.

      The console output is list as below:

      ... skipped ...

      [TASKS] Skipping maven reporter: there is already a result available.
      [JENKINS] Recording test results
      [JENKINS] Archiving D:\AppData\jenkins\jobs\pac\workspace\pac-core\pom.xml to D:\AppData\jenkins\jobs\pac\modules\pac$pac-core\builds\2011-06-20_18-25-35\archive\pac\pac-core\1.0-SNAPSHOT\pac-core-1.0-SNAPSHOT.pom
      [INFO] ------------------------------------------------------------------------
      [ERROR] BUILD ERROR
      [INFO] ------------------------------------------------------------------------
      [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-surefire-plugin:2.4.3:test': hudson.util.io.ParserConfigurator$1; local class incompatible: stream classdesc serialVersionUID = 6472613931861772577, local class serialVersionUID = -2178106894481500733
      [INFO] ------------------------------------------------------------------------
      [INFO] For more information, run Maven with the -e switch
      [INFO] ------------------------------------------------------------------------
      [INFO] Total time: 1 minute 50 seconds
      [INFO] Finished at: Mon Jun 20 18:27:29 CST 2011
      [INFO] Final Memory: 97M/263M
      [INFO] ------------------------------------------------------------------------
      Waiting for Jenkins to finish collecting data

      ... skipped ...

          [JENKINS-10030] Builds fail in JUnit test archiving (since 1.416) if specifying JDK other than the container

          Pei-Tang Huang created issue -

          Our Jenkins installation runs under 'Oracle JRE 1.6.0 build 24',
          and the configured JDK in Jenkins is 'IBM J9 VM build 2.4, JRE 1.6.0'...

          Pei-Tang Huang added a comment - Our Jenkins installation runs under 'Oracle JRE 1.6.0 build 24', and the configured JDK in Jenkins is 'IBM J9 VM build 2.4, JRE 1.6.0'...

          Problem remains in 1.417.

          Once I set JDK of jobs to the same of the container,
          those previously failed builds became stable...

          But this is not a valid option in our case,
          We MUST specify the JDK to fit our production environments.

          Pei-Tang Huang added a comment - Problem remains in 1.417. Once I set JDK of jobs to the same of the container, those previously failed builds became stable... But this is not a valid option in our case, We MUST specify the JDK to fit our production environments.
          Pei-Tang Huang made changes -
          Summary Original: hudson.util.io.ParserConfigurator anonymous inner class serialzation error in jenkins 1.416 New: Maven build fail (since 1.416) for specifying JDK other than the container
          Fred G made changes -
          Link New: This issue is related to JENKINS-10058 [ JENKINS-10058 ]

          Gareth King added a comment -

          Thank you for indicating a workaround.

          We are also experiencing this problem, and this is a big problem for us too as we target 2 different JDK's.
          The JDK's are targeted depending on the app server and it's underlying JDK (Websphere 6.1 and Websphere 7)

          Gareth King added a comment - Thank you for indicating a workaround. We are also experiencing this problem, and this is a big problem for us too as we target 2 different JDK's. The JDK's are targeted depending on the app server and it's underlying JDK (Websphere 6.1 and Websphere 7)

          Thorsten Roemer added a comment - - edited

          Same goes here for our AIX slaves using IBM JDK 1.6.
          (Jenkins v1.419)

          Creepy workaround is to use "Publish TestNG Results" (Plugin) rather than "Publish JUnit Results".

          Thorsten Roemer added a comment - - edited Same goes here for our AIX slaves using IBM JDK 1.6. (Jenkins v1.419) Creepy workaround is to use "Publish TestNG Results" (Plugin) rather than "Publish JUnit Results".

          micha4311 added a comment - - edited

          This also occurs on Jenkisn 1.423 running on Sun JDK 1.6.0_15, Slave on 1.6.0_26, Build Job running with IBM JDK 1.5.
          Currently all IBM Builds are not working, so this is a blocking issue!

          micha4311 added a comment - - edited This also occurs on Jenkisn 1.423 running on Sun JDK 1.6.0_15, Slave on 1.6.0_26, Build Job running with IBM JDK 1.5. Currently all IBM Builds are not working, so this is a blocking issue!
          micha4311 made changes -
          Priority Original: Major [ 3 ] New: Blocker [ 1 ]

          micha4311 added a comment -

          What about the workaround - I do not find a "Publish JUnit Results" in the job configuration which I could deactivate. Does this come with the testng-plugin (is this the testng-plugin on the jenkins page?)

          micha4311 added a comment - What about the workaround - I do not find a "Publish JUnit Results" in the job configuration which I could deactivate. Does this come with the testng-plugin (is this the testng-plugin on the jenkins page?)

            kutzi kutzi
            beta Pei-Tang Huang
            Votes:
            8 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: