• Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Critical Critical
    • None
    • Jenkins 1.580.2, RHEL 6.3

      I'm using the plugin to clone the workspace of another job (surprise, surprise). When doing this, I get (Console output):

      Started by user Lenz, Olaf
      [EnvInject] - Loading node environment variables.
      Building on master in workspace /data_ssd/jenkins/jobs/OL-coverity-ST8-build-s2/workspace
      Restoring workspace from build #59 of project OL-coverity-ST8-build
      FATAL: null
      java.lang.NullPointerException
      	at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:894)
      	at hudson.model.AbstractBuild.access$600(AbstractBuild.java:104)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:634)
      	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
      	at hudson.model.Run.execute(Run.java:1745)
      	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      	at hudson.model.ResourceController.execute(ResourceController.java:89)
      	at hudson.model.Executor.run(Executor.java:240)
      

          [JENKINS-26500] NPE after restoring workspace

          Olaf Lenz added a comment -

          I had a look into the source code at https://github.com/jenkinsci/jenkins/blob/jenkins-1.580.2/core/src/main/java/hudson/model/AbstractBuild.java
          Line 894 is:

          return scm.parse(this,changelogFile);

          As changelogFile is used directly before, this means that "scm" is null...

          Olaf Lenz added a comment - I had a look into the source code at https://github.com/jenkinsci/jenkins/blob/jenkins-1.580.2/core/src/main/java/hudson/model/AbstractBuild.java Line 894 is: return scm.parse(this,changelogFile); As changelogFile is used directly before, this means that "scm" is null...

          Olaf Lenz added a comment -

          I have identified the root of the problem, and it is not a problem of the clone workspace plugin, but of the shell-script-scm plugin that I have been using, which doesn't create a changelog and does not provide a corresponding parser, so I will close the bug.

          Olaf Lenz added a comment - I have identified the root of the problem, and it is not a problem of the clone workspace plugin, but of the shell-script-scm plugin that I have been using, which doesn't create a changelog and does not provide a corresponding parser, so I will close the bug.

          Olaf Lenz added a comment -

          Not a problem of this plugin, but of the shell-script-scm plugin.

          Olaf Lenz added a comment - Not a problem of this plugin, but of the shell-script-scm plugin.

            Unassigned Unassigned
            olenz Olaf Lenz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: