[JIRA] [clone-workspace-scm-plugin] (JENKINS-26518) Cannot clone workspace that was created using ssscm

Tue, 20 Jan 2015 23:48:07 -0800

Issue Type: Bug Bug
Assignee: nobody
Components: clone-workspace-scm-plugin, shell-script-scm-plugin
Created: 21/Jan/15 7:47 AM
Description:

When trying to clone a workspace that was produced by a job using the shell-script-scm plugin, the cloning job produces the following NPE:

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)



The shell-script-scm plugin does not produce a changelog and doesn't provide a parser for the changelog. However, the "clone workspace SCM" requires a changelog parser. Therefore, both plugins cannot work together.



I believe that this should be fixed in both plugins: the clone workspace plugin should handle the case when the changelog parser is null, and the ssscm should return  "hudson.scm.NullSCM" instead of null.
Environment: Jenkins 1.580.2 (LTS)
Project: Jenkins
Priority: Critical Critical
Reporter: Olaf Lenz
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to