Guys,

I'll resolve this issue for now as a local fix.

I greatly appreciate your help and patience regarding this one.

On a side note - Bamboo on the 'polling strategy' should not constantly poll if the svn update operation fails. I have made some changes so that the connection attempts at least obey the polling interval.

Cheers,
Edwin

Daniel,

Thanks for the update about this!

I have done some testing locally, and with your logs, I figured that the problem is actually deleting the contents of the folder itself that is the problem. In subversion, each file system folder contains a hidden .svn folder which holds SVN info about that particular directory.

I am guessing in your instance, this hidden .svn folder is being removed by the build, and hence the error.

Cheers,
Edwin

Allright! I found it:

An empty folder under revision control was deleted by the build process. Apparently this lead to svn sync problems.

IMHO this issue may be closed.

Thank you, guys!

Hi,

as a workmate of Daniel I try to give some more input:

• The svn server does not have any log files yet as svnserve lacks this feature so far as far as I know.
• I should add that our svn server 1.3.2 (r19776). is currently on a Windows platform.
• We only have this problem with one single project.
• Of course we checked the repository with the subversion checks, everything is fine. With all other clients (command line, Tortoise, Idea) there are no problems so far.
• The problem occurs with svn update comand of bamboo. The activity log file gives something like the following, repeated after some seconds:

02-Apr-2007 16:31:17 Failed to get the build source code:B2 - Default
02-Apr-2007 16:31:20 Updating Subversion source code from version 166 to version 169
02-Apr-2007 16:31:20 Cleaning up subversion repository due to previous RepositoryException

• We access Subversion through https whith a stored self signed key in the Java keystore and whithout username/password as it is free for the Bamboo server to enter (ip based) - but as this works on the same Bamboo instance for the other projects I don't think there should be a problem with this.
• I just upgraded to 1.0.3 and the error still persists.

I will attach a current bamboo.log.

Best,

Caspar.

Hi Daniel,

That is strange indeed. I presume this is something that is consistently happening on that project?

Actually, it would be great if you could pass along the following two logs as well:

1) the whole atlassian-bamboo.log
2) the server SVN logs.

By the way, would the subversion server be publicly available by any chance so that we can try o connect from here?

Cheers,
Edwin

Edwin,

we access the svn server via https. Funny thing: the other projects build with no problem at all using the same svn server. Is there another log somewhere which we could send you?

Hi Daniel,

Apologies for taking so long to get back to you. Bamboo currently runs on a SVNKit (Java SVN) which supports SVN 1.4.2.

Locally, our servers are running on 1.3.2 and we haven't been able to reproduce this issue here.

I was also wodering which protocol you are using for SVN? (http, https, svn+ssh?) Also, can yo successfully checkout and update your source code on the bamboo machine with another Subversion client?

Cheers,
Edwin

Me too.

Please specify svn client version used by bamboo!

We use 1.3.2 (r19776) on the server and 1.3.5 clients.

Observed after deleting artifacts from the repo.

The issue still exists after removing the TortoiseSVN client from the workstation.

We are using Subversion 1.3.0 R179 for our server. The the clients committing are 1.4.2.

There seems to be a "Sync" processing in update subversion source code that is causing the error. (When a client checks in).

My concern is that the TortisonSVN client on the machine may be corrupting the file system. I am in the process of un-installing it. When I delete the files via the Bamboo console, and manually initiate a build (which triggers a complete download from SVN), the build works fine. It reminds me of an interaction issue when using eclipse that I have encountered from a development machine before. I will send a folloup email with what I find.

Thanks
Ken