[
https://issues.jenkins-ci.org/browse/JENKINS-11370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158821#comment-158821
]
sid nancy commented on JENKINS-11370:
-------------------------------------
Here is the full stacktrace from the console when the pre-scm build plugin
tries to reference the non-existent workspace. This will happen any time a new
job which has no namespace in the slave filesystem uses the pre-scm plugin.
Started by user <username>
Building remotely on <slave node> in workspace /some/path/on/slave
Running Prebuild steps
[<job name>] $ cmd /c call
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\hudson334444854237146312.bat
The directory name is invalid
FATAL: command execution failed
java.io.IOException: Cannot run program "cmd" (in directory
"/some/path/on/slave"): CreateProcess error=267, The directory name is invalid
at java.lang.ProcessBuilder.start(Unknown Source)
at hudson.Proc$LocalProc.<init>(Proc.java:244)
at hudson.Proc$LocalProc.<init>(Proc.java:216)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:707)
at hudson.Launcher$ProcStarter.start(Launcher.java:338)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:932)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:899)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1$1.run(Engine.java:60)
at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: CreateProcess error=267, The directory name is
invalid
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(Unknown Source)
at java.lang.ProcessImpl.start(Unknown Source)
... 17 more
Failed build for hudson.tasks.BatchFile@535c37ae
> pre-scm-buildstep assumes workspace exists
> ------------------------------------------
>
> Key: JENKINS-11370
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11370
> Project: Jenkins
> Issue Type: Bug
> Components: plugin
> Affects Versions: current
> Environment: OS X
> Reporter: Niklas Saers
> Priority: Minor
>
> pre-scm-buildstep assumes that the directory workspace exists when it's
> running. However, when setting up a project, it does not exist, and thus this
> step will fail unless the admin creates manually. Proper behaviour should be
> to check if it exists, and create it if it doesn't. Otherwise, if it does not
> exist, the execute shell will fail
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
