The console output of the job including the stacktrace is sufficient to explain the cause of the problem.

There is an assumption in the plugin that there were changes which triggered the build, and the cause of the exception is that there were no changes. The triggering job was manually triggered.

The solution is either to have the multiple-scm plugin not return null for changes() or to have the clone-workspace-scm accept null for a changeset.

Started by upstream project "Concordance Trigger" build number 3
Building remotely on Java6 in workspace /home/jenkins/java6_slave/workspace/Concordance
Checkout:Concordance / /home/jenkins/java6_slave/workspace/Concordance - hudson.remoting.Channel@1c32b82:Java6
Using strategy: Default
Last Built Revision: Revision 025dcdbe80a53467cf7cfac9de33c08aa7e77e13 (oshell_origin/staging)
Checkout:OShell / /home/jenkins/java6_slave/workspace/Concordance/OShell - hudson.remoting.LocalChannel@13c7b26
Cloning the remote Git repository
Cloning repository oshell_origin
Fetching upstream changes from ssh://git@ken-desktop/revision_control/git/OShell
Commencing build of Revision 025dcdbe80a53467cf7cfac9de33c08aa7e77e13 (oshell_origin/staging)
Checking out Revision 025dcdbe80a53467cf7cfac9de33c08aa7e77e13 (oshell_origin/staging)
Restoring workspace from build #3 of project Concordance Trigger
FATAL: null
java.lang.NullPointerException
at hudson.plugins.cloneworkspace.CloneWorkspaceSCM.createChangeLogParser(CloneWorkspaceSCM.java:185)
at org.jenkinsci.plugins.multiplescms.MultiSCMChangeLogParser.<init>(MultiSCMChangeLogParser.java:40)
at org.jenkinsci.plugins.multiplescms.MultiSCM.createChangeLogParser(MultiSCM.java:155)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:583)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:468)
at hudson.model.Run.run(Run.java:1410)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)