来自Jenkins的执行Windows批处理命令失败，但在cmd.exe中运行正常

Question

I am trying to run this command in jenkins after a MSbuild

xcopy "C:\Program Files (x86)\Jenkins\workspace\trunk\Projects\results\results\obj\Debug\Package\PackageTmp" "Y:\Extraction_Zone\Jenkins\" /E 

Y: is a mapped network drive. This runs fine in cmd.exe but when trying to run it in Jenkins, I am getting the error Invalid drive specification .

Here is the output from jenkins:

Time Elapsed 00:00:04.03
[trunk] $ cmd /c call C:\Windows\TEMP\hudson3389873107474371072.bat

C:\Program Files (x86)\Jenkins\workspace\trunk>xcopy "C:\Program Files (x86)\Jenkins\workspace\trunk\Projects\results\results\obj\Debug\Package\PackageTmp" "Y:\Extraction_Zone\Jenkins\" /E 
Invalid drive specification
0 File(s) copied

C:\Program Files (x86)\Jenkins\workspace\trunk>exit 4 
Build step 'Execute Windows batch command' marked build as failure
Finished: FAILURE

Any help would be appreciated.

Answer 1

I too had a similar issue once. Try granting the Jenkins service "Logon as This account" right under services.msc and make sure the account you type there is the same as the one you use for running cmd.exe .

Answer 2

These commands based on Java JAR files worked for me:
cmd
net use x: \\\\
xcopy "dist\\" x:\\ /Y

And that's it! I spent lot of time figure out this issue and nothing worked until I wrote CMD and NET USE!
Neither I didn't need to change permission on jenkins service nor use runas command.

But I must mention that everyone had read and write access to the network drive.

Answer 3

I had the same issue with my Windows Task running a batch file (I know it is not exactly same) where I tried to copy file to network location ie shared drive. I used the UNC path and mapped drive as well but the error was same. For me it was error number 4 - MS DOS error code. The solution was to use net use command! Hope that it helps.

Answer 4

Easy fix for most things.

1. Make a batch command with what your trying to run, filename.bat with the command prompt text inside.
2. Make a normal windows shortcut for the batch command, edit the shortcuts advanced properties and check the "Run as admin" (tricky tricky).
3. Now run the filename.lnk shortcut from jenkins command line call, this will get you around all the jazz.

:)

Answer 5

The solution of adarshr (ie, modifying the log on credentials of the service) has worked for me for a part of the problem: in my case, this allowed me to successfully check out a mercurial repository (using ssh protocol), which I could not do when using 'Local System account'.

However, I still have different behavior between running a command-line script or running the same script from a jenkins 'execute shell' script in the build section. In my case, I compile a Python extension. In Jenkins, I cannot import the extension (I don't see any error, but the execution simply stops, so I suspect it crashes).

If I uninstall the service and run the slave agent as a Java Web Start, I do get the same behavoir. It is a temporary fix for me, but it means that when I reboot the windows build machine, I have to manually re-start the Java Web Start application.

So -at least in my case- it is clear that this is a credential problem.

Credentials usage documentation: https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI

Answer 6

我用CIFS插件解决了我的问题。

Answer 7

Faced similar issue and found two ways to solve.

Type 1: Tell Jenkins about mapped drive. 1.Goto -> Manage Jenkins -> Script Console (Groovy Script). 2.Run below command

 def mapdrive = "net use Y: \\\\copy_nework_address"
 mapdrive.execute();
 println "net use".execute().getText()

Type:2 1.Goto -> cmd -> run "net use" to know network address

xcopy "C:\Program Files (x86)\Jenkins\workspace\trunk\Projects\results\results\obj\Debug\Package\PackageTmp" "Copy_Network_Address\Extraction_Zone\Jenkins\" /E

Conclusion:- I prefer 2nd types as after every restart i should run Groovy Script.