Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Bamboo not connecting to mapped drive Edited

Hi,

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 ${bamboo.build.working.directory}

echo copying the release from centos to release folder

xcopy /s /i /y X:\cdk.pl ${bamboo.build.working.directory}\releases\64Bit

rem xcopy /s /i /y ${bamboo.build.working.directory}\releases\64Bit\cdk.pl %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,

Mark.

1 answer

0 votes

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.

thanks.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

223 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you