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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bamboo Error: Parent Directory Doesn't Exist for Branch Build

I get the following error for a branch based build. 

10-Sep-2018 20:21:23

{:timestamp=>"2018-09-10T20:21:23.941063+0000", :message=>"Parent directory does not exist: javelin2_0.3.3-1.20180910202123.bugfix - cannot write to javelin2_0.3.3-1.20180910202123.bugfix/CN-2152-javelin-is-unable-to-provision-vms_amd64.deb", :level=>:fatal}

All other parameters are the defaults. I've done alot of searching but am not able to find anything addressing this error. 

1 answer

1 accepted

0 votes
Answer accepted
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 12, 2018

Hey Tim,

Can you share with us were this error was observed and the set of steps taken to reproduce it?

Possible troubleshooting steps:

  1. Find differences between branches that work and this one.
  2. Clone this branch from outside Bamboo and verify if you will experience any error.
  3. If your repository is not that big, try to clean the repository cache: *Cog icon >> Overview >> Repository settings*.
  4. Try to navigate to that folder and check the permissions involved. Is the user running the agent/server able to edit that folder?

Please share with us your findings.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events