The system cannot find the specified drive in Jenkins

Question

I want to copy some files from a network shared drive (mounted at my local machine as drive Z). I have written a Batch file to copy the contents of Z drive into my local drive.

Answer 1

If you don't want to use Jenkins-plugins or schedule-Tasks here is a "groovy" way:

By Hand:

You can use the Groovy Script-Console provided by Jenkins>Manage Jenkins>Script Console and execute the command to map the network-drive within the Jenkins-service. (Must be repeated, once the Jenkins-service is stopped)

Automation:

Write your Groovy commands to a file named "init.groovy" and place it in your JENKINS_HOME-directory. So the network-drive gets mapped on Jenkins-startup.

Groovy Commands - Windows:

Check available network drives using the Script-Console:

println "net use".execute().getText()

Your init.groovy would look like this:

def mapdrive = "net use z: \\\\YOUR_REMOTE_MACHINE\\SHARED_FOLDERNAME"
mapdrive.execute()

Answer 2

In order to access your remote drive

just use the command in cmd prompt

---

• pushd "\sharedDrive\Folder1\DestinationFolder"

• mkdir FolderName

• popd

---

pushd >> It navigates to the shared drive by creating a virtual drive.. popd >> Gets you back to the local directory

Answer 3

I was trying to copy files from one remote computer to other, the easy solution which worked for me is COPY iphone.exe \192.xx.xx.xx\dev(dev is the folder name on c drive in that ip address)

Answer 4

A similar issue showed up for us on Jenkins slaves set up on Windows Server 2008 following this documentation. The Jenkins agent failed to access the mounted network drives even after configuring the agent service with the correct user credentials.

Troubleshooting:

1. Jenkins could access the mounted network drives by their drive letters when connected via the JNLP agent (Launch agent via Java Web Start).
2. It stops recognizing the drive letters soon after we install the agent as a Windows service. Configuring the correct user credentials and restarting the agent does not help.
3. We could still access the drives via the command line while logged in to the machine with the above user.
4. Stop the agent service from services.msc and then uninstall it by running the command jenkins-slave.exe uninstall. The slave is disconnected at this point.
5. Reconnect the slave by launching the JNLP agent via Java Web Start. The agent can now access the network drives again.

Synopsis:

Do not install the slave agent as a Windows service to keep accessing your mounted network drives using drive letters. But this is highly unreliable as the agent might fail to restart after a machine reboot. Alternatively, see if Jenkins can access them via \\<ip_address\of\network\drive>.

Answer 5

Try adding debugging commands to that bat file, or as separate build step, such as net use, set (pay attention to vars like like HOMEPATH and USERNAME) and plain dir Z:\.

As said in another answer, most likely reason is that Jenkins runs as SYSTEM user, which has different permissions. One way around that is, go to services (for example open Task Manager, go to Services tab in it, click the Services button at the lower right corner of that tab), find Jenkins service, open it's properties, go to "Log on" tab and set your normal user account as one that runs Jenkins.

Answer 6

Had this issue where my jenkins job was unable to read files present on the network drive. I resolved it by adding "net use" command in your pre-build step. i.e.

Open your job. Go to Pre Steps From the drop down, select Execute Windows Batch Command Enter the following command: net use E: \[server name][Folder name] "[password]" /user:"[userid]" Click Save Execute the job

I was able to read files from my network drive by following the steps mentioned above.

It seemed to be a one time activity as after the initial run, I had removed the batch command from my job and it seemed to remember the mapped drive command.