Jenkins batch command error : ...system cannot find the file specified...

[dmatrix]

Hello,

My environment is Jenkins1.506/VS&TFS2010

I was testing "Add Build Step" for MSBuild Plug-In with a simple "Execute Windows batch command" and got this:

[GAtest1] $ cmd /c call C:\Windows\TEMP\hudson8854542679623085192.bat

C:\Program Files (x86)\Jenkins\workspace\GAtest1>echo test 
test

C:\Program Files (x86)\Jenkins\workspace\GAtest1>COPY D:\drop\test.txt D:\testdir\ 
The system cannot find the file specified.

The build was successful and the echo command was good, except the COPY command.

Anyone has this same issue before?

Thanks,

[Mark Waite]

I think that is saying that the built-in command "COPY" in the Windows command processor tried to copy from D:\drop\test.txt to D:\testdir\ and either found that D:\drop\test.txt did not exist, or D:\testdir\ did not exist.

The preceding "echo" command did not create D:\drop\test.txt, so I assume it might not exist.

The preceding "echo" command did not create D:\testdir\, so I assume it might not exist as well.

Mark Waite

---

From: dmatrix <micha...@gmail.com>
To: jenkins...@googlegroups.com
Sent: Thursday, March 21, 2013 3:57 PM
Subject: Jenkins batch command error : ...system cannot find the file specified...

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

[dmatrix]

Thanks for your response Mark,

No, I created the \testdir and test.txt in D:\ to test, they are there, and I also checked the spaces in the command.

The funny thing is I did a COPY and CALL command before, in my previous job with similar environment, and Jenkins had no problem

at all.  Currently, I tried double and single quote and Jenkins still insist on not seeing the file.   

I sure don't have problem running this command on the dos prompt.  

[dmatrix]

Thanks for your response Mark,

No, I created the \testdir and test.txt in D:\ to test, they are there, and I also checked the spaces in the command.

The funny thing is I did a COPY and CALL command before, in my previous job with similar environment, and Jenkins had no problem

at all.  Currently, I tried double and single quote and Jenkins still insist on not seeing the file.   

I sure don't have problem running this command on the dos prompt.  

On Thursday, March 21, 2013 3:46:19 PM UTC-7, Mark Waite wrote: