TeamCity SVN Checkout Failing Due to File Locks

2
votes

This is my first TeamCity project, and I am having an issue with SVN checkout.

Here are my settings for the SVN checkout from within TeamCity:

  • VCS Checkout Mode - Automatically on Agent
  • Checkout Directory - C:\BuildCheckouts[Project Name]
  • VCS Labelling mode - Do Not Label
  • Externals Support - Full Support
  • Default Config Directory - Use Default Directory
  • Working Copy Format - 1.5

On my first run of the build, everything runs fine, checkout occurs, and the build continues. On my second checkout, however, the build fails and I get the following error message:

[03:31:28]: Updating sources: Agent side checkout... (1s)
[03:31:30]: [Updating sources: Agent side checkout...] Failed to perform checkout on agent: org.tmatesoft.svn.core.SVNException: svn: Error during update from http://[Server Name]/svn/[Project Name] to C:\BuildCheckouts\[Project Name]
svn: Cannot create new file 'C:\BuildCheckouts\[Project Name]\Tools\.svn\lock': Access is denied

I have tried searching for this specific error, and came up with this old article (2003), but it does not seem to apply since I am using NTFS as my file system.

Since my build script runs tests after compiling, I need the externals downloaded to the checkout directory along with the actual code.

Are my configuration settings incorrect?

2
svncontinuous-integrationteamcity
Does the user the TeamCity build agent runs under have modify and delete access to that directory, or just create? – Lasse V. Karlsen
Also have you tried doing a svn clean before the checkout? – AutomatedTester
I'd be tempted for your first TeamCity project to not try and change all the settings - why not just leave the checkout directory blank so that TeamCity uses its default? – David M
@David M - It must have been a directory/file Permissions issue. I switched the checkout directory to the default, and the project ran successfully multiple times. – Mark Struzinski

2 Answers

1
votes

Try running the Teamcity service under the specific user account which has permissions to modify files on the machine. We are doing so and haven't faced this issue.

0
votes

TeamCity's build agent runs under specific user (check settings of the windows service for the build agent).

So, this user should have full access to the C:\BuildCheckouts directory and below.