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

Buil-flow jobs fail to load the job history if the envinject plugin is installed

      Steps to reproduce :
      1.Install build-flow and envinject
      2.Create a build-flow job
      3.Successfully run the build-flow job
      4.Restart jenkins

      The following occurs:
      No builds will be displayed in the history. Relevant jenkins log entry is attached.

      08.08.2012 12:33:25 hudson.model.RunMap load
      WARNING: could not load E:\Jenkins\jobs\test111\builds\2012-07-31_17-20-02
      hudson.util.IOException2: Unable to read E:\Jenkins\jobs\test111\builds\2012-07-31_17-20-02\build.xml
      at hudson.XmlFile.unmarshal(XmlFile.java:164)
      at hudson.model.Run.reload(Run.java:290)
      at hudson.model.Run.<init>(Run.java:279)
      ....
      Caused by: com.thoughtworks.xstream.converters.ConversionException: Could not call org.jenkinsci.plugins.envinject.EnvInjectPluginAction.readResolve() : null : Could not call org.jenkinsci.plugins.envinject.EnvInjectPluginAction.readResolve() : null
      ---- Debugging information ----
      message : Could not call org.jenkinsci.plugins.envinject.EnvInjectPluginAction.readResolve() : null
      cause-exception : com.thoughtworks.xstream.converters.reflection.ObjectAccessException
      cause-message : Could not call org.jenkinsci.plugins.envinject.EnvInjectPluginAction.readResolve() : null
      class : com.cloudbees.plugins.flow.FlowRun
      required-type : org.jenkinsci.plugins.envinject.EnvInjectPluginAction
      path : /com.cloudbees.plugins.flow.FlowRun/builds/edgeMap/entry/org.jgrapht.graph.IntrusiveEdge/target/actions/org.jenkinsci.plugins.envinject.EnvInjectPluginAction
      line number : 59
      -------------------------------

      Note:
      Manually deleting all lines containing "envinject" from Jenkins\jobs\test111\builds\2012-07-31_17-20-02\build.xml allows for the build to properly be loaded and displayed in the build history.

        1. 44-jenkins.err.log
          8 kB
        2. build-edited.xml
          6 kB
        3. build-original.xml
          6 kB
        4. jenkins.err.log
          8 kB

          [JENKINS-14728] Buil-flow jobs fail to load the job history if the envinject plugin is installed

          Andrei Ababei added a comment -

          Attached "build-original.xml" the load error and "build-edited.xml" edited to remove the envinject stuff

          Andrei Ababei added a comment - Attached "build-original.xml" the load error and "build-edited.xml" edited to remove the envinject stuff

          Code changed in jenkins
          User: Gregory Boissinot
          Path:
          src/main/java/org/jenkinsci/lib/envinject/EnvInjectAction.java
          http://jenkins-ci.org/commit/envinject-lib/38e2c3f2b10388328a38dbc553f217ca75fdd5e5
          Log:
          More tolerant to avoid loading errors
          (JENKINS-14728)

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/lib/envinject/EnvInjectAction.java http://jenkins-ci.org/commit/envinject-lib/38e2c3f2b10388328a38dbc553f217ca75fdd5e5 Log: More tolerant to avoid loading errors ( JENKINS-14728 )

          Could you check if the following version of the EnvInject plugin fix the issue?
          https://buildhive.cloudbees.com/job/jenkinsci/job/envinject-plugin/ws/target/

          Gregory Boissinot added a comment - Could you check if the following version of the EnvInject plugin fix the issue? https://buildhive.cloudbees.com/job/jenkinsci/job/envinject-plugin/ws/target/

          Andrei Ababei added a comment -

          The workspace was empty so I just took the artifacts from the last build (#44). In Jenkins it shows up as 1.67-SNAPSHOT (private-08/08/2012 19:37-jenkins).

          With that version of the plugin the issue is still present and the error log (attached) is unchanged.

          Andrei Ababei added a comment - The workspace was empty so I just took the artifacts from the last build ( #44 ). In Jenkins it shows up as 1.67-SNAPSHOT (private-08/08/2012 19:37-jenkins). With that version of the plugin the issue is still present and the error log (attached) is unchanged.

          Yes, try this version
          Thanks

          Gregory Boissinot added a comment - Yes, try this version Thanks

          Andrei Ababei added a comment - - edited

          The bug is still present on build #44 aka 1.67-SNAPSHOT (private-08/08/2012 19:37-jenkins).

          Andrei Ababei added a comment - - edited The bug is still present on build #44 aka 1.67-SNAPSHOT (private-08/08/2012 19:37-jenkins).

          Could you attach your job configuration file (config.xml)?
          I'll try to reproduce it.

          Gregory Boissinot added a comment - Could you attach your job configuration file (config.xml)? I'll try to reproduce it.

          Andrei Ababei added a comment -

          I updated to the official 1.67 and the bug is fixed (the history is now displayed).

          The bad news is that the way it was fixed results in another less serious bug (a chart is missing). I will submit another bug for it shortly.

          Andrei Ababei added a comment - I updated to the official 1.67 and the bug is fixed (the history is now displayed). The bad news is that the way it was fixed results in another less serious bug (a chart is missing). I will submit another bug for it shortly.

          Regarding the last comment, set to fix

          Gregory Boissinot added a comment - Regarding the last comment, set to fix

            ndeloof Nicolas De Loof
            thunderm Andrei Ababei
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: