Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Bamboo not connecting to mapped drive

Mark Beynon July 16, 2018


I have a Bamboo inline script that does not connect to the the mapped X drive and gives the error;

16-Jul-2018 15:30:080 File(s) copied
16-Jul-2018 15:30:08Invalid drive specification

The script;

@echo on
set copycmd=/Y
echo working dir ${}

echo copying the release from centos to release folder

xcopy /s /i /y X:\ ${}\releases\64Bit

rem xcopy /s /i /y ${}\releases\64Bit\ %SdriveHF2%\64bit

The drive is mapped correctly on the host machine and the xcopy command works from the command line using xcopy.

The mapping is to a unix box. This used to work but I suspect a recent upgrade to Bamboo has broken things.

Bamboo version information

Version 5.15.5

Build number 51518

Build date 3/28/17

Many thanks,


1 answer

0 votes
Gabriel Ribeiro
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 20, 2018

Hi Mark,

I'm not sure if the upgrade itself is responsible for the issue you're seeing. Script tasks are external processes and Bamboo has no control over what is happening there.

What could possibly be happening in your case is that the user you're using to start the Bamboo service doesn't have the X: drive mapped, since the script will run using this same user, the xcopy command will fail.

Based on the description you provided, I'm assuming you're running Bamboo on a Windows machine so, you can try to start the service with a local user and make sure the X drive will be available for this specific user during the build execution. You will find the instructions on how to change the user used to start Bamboo in the documentation below:

let us know the result.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events