-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins 1.565.3
OS: Ubuntu 12.04 LTS (x68)
Perforce Server: 14.1
After updating to 1.3.29, we noticed that when we have jobs with the 'Run Parameter', the Perforce plug-in throws a NPE when trying to calculate the effective workspace name.
The stack trace printed out by Jenkins is a:
[sample-run-parameter-job] $ p4 workspace -o sample-run-parameter-job
Caught exception in perforce-plugin. nulljava.lang.NullPointerException
at java.lang.String.replace(String.java:2219)
at hudson.plugins.perforce.utils.MacroStringHelper.substituteParametersNoCheck(MacroStringHelper.java:185)
at hudson.plugins.perforce.utils.MacroStringHelper.getDefaultSubstitutions(MacroStringHelper.java:341)
at hudson.plugins.perforce.utils.MacroStringHelper.substituteParametersNoCheck(MacroStringHelper.java:246)
at hudson.plugins.perforce.utils.MacroStringHelper.substituteParametersNoCheck(MacroStringHelper.java:298)
at hudson.plugins.perforce.utils.MacroStringHelper.substituteParameters(MacroStringHelper.java:148)
at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:876)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1252)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:615)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:524)
at hudson.model.Run.execute(Run.java:1706)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:232)
ERROR: Caught exception in perfoce-plugin. null
- is related to
-
JENKINS-25737 'Run Parameter' build parameter is null when SCM/pre-SCM phase is started on remote-node.
- Open
- links to