bamboo v5.4.1: Unable to clean source directory ...unable to delete file *\.svn\wc.db

Hello everyone,

I am having this problem with several projects plans , the build fail because the system fail to clean the project ==> it fail to delete subversion related file wc.db .

is there any solution or work around for this ?

now I go manually and delete the .svn folder.


8 answers

0 votes
Timothy Chin Community Champion Apr 29, 2014

Does the user running Bamboo have permission to that file?

0 votes

Hi Hussain,

Would be possible to inform in which Operational System Bamboo is running on, please? Due to what you have informed on your comment , it seems you are running Bamboo on a Linux / Mac OS environment.

If you go to the Plan Configuration >> Stages, select your stage created and click on Tasks tab there is an option in the task "Source Code Checkout configuration" that removes the source directory and checks it out again prior to each build. This may significantly increase build times ([ ] Force Clean Build).

Another option would be under Plan Configuration >> Stages, select your stage created and click on Miscellaneous tab. You will find an option that removes the source directory after each build. This may increase build times but save disk space. ([ ] Clean working directory after each build).

Alternatively, you can create an Script tasks to delete the folder/file you want.

// the following command will delete a directory recursively
rm -rf /<path>/<to>/<directory>

Kind regards,

I had run into this issue which occurs when trying to delete a particular subdirectory in deployment projects. Like Rafael mentioned, I had to add a script that does exactly that.

However, since we have nearly 200 deployment plans, this will be quite tedious and to be honest, extremely frustrating to even have to do this.

C'mon Atlassian, is this currently a tracked bug?

0 votes

Hi guys,

I would kindly ask you to:

  1. run the task once again (this will generate new entries to the logs files)
  2. open up <bamboo-home>/logs/atlassian-bamboo.log
  3. post the stacktrace where the issue happens

Alternatively, I would suggest you on:

  • running the task once agian (this will generate new entries to the logs files)
  • creating a support request under Bamboo administration >> System >> Atlassian Support Tools >> Support Request
    Please check all options under Support Data to Attach before submitting your Support Request.

Kind regards,

Hi Everyone , thanks for the replies.. I am running Bamboo on Windows and it is runing as a windows service using the local system account.. the fact that this happen with only subversion special files that get created automatically when Bamboo checkout the code ..make me wonder if there is a special config to do that will make Bamboo work better with subversion.

I will create a support request the next time this happen, now I deleted that folder manually .

Thanks Rafael and everyone else here.

We're also experiencing this issue. Though we have ~10 agents that could run this job so it only seems to fail when it is run on an agent that has already run the job. Any ideas?

And yes, the agents have permission to the directory.

It sounds like something is holding a handle open. is supposed to be able to help you identify stuck handles (I'm not a windows person though so...)

0 votes

Chances are it's your antivirus that locks that file. Can you try excluding that directory from antivirus?

Worthy suggestion. Putting an exception in place.

Some success implementing scripts that clean the location before the build begins...

Not optimal.

I get this problem if the source directory contains file/directory names consisting of non-UTF-8 characters.

My client has the same issue...I checked to see which process was holding the lock on the file in question and it's the bamboo remote agent service.


So this is a bamboo bug...what is the process my client should go through to progress a fix for this?

First upgrade to a more recent version of Bamboo, it contains a newer version of svnkit library, which will likely fix your issue. If it does not, open a support request at


Suggest an answer

Log in or Join to answer
Community showcase
Renan Battaglin
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,066 views 0 5
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot