Renaming subversion folders

Hi,

Wondered if anyone has had any experience with renaming subversion folders and how to get TeamCity to handle this.

I setup some projects and configured server checkout mode, using an inclusive checkout rule to pull down content from SVN.

After renaming the folder in SVN (and the corresponding config in the TC project) the build fails with the following error:

[15:22:33]: Patch is broken, can be found in file: /usr/local/Saga/dev/libra_dev/tc_6.0.1/TeamCity/buildAgent/temp/cache/temp4496833232154501050patch_197
[15:22:33]: Failed to build patch for build #18 {build id=197}, VCS root: svn: http://canary.saga.co.uk:81/svn/TheVault/Taurus/trunk {id=2}, due to error: Unknown path kind: none for http://canary.saga.co.uk:81/svn/TheVault/Taurus/trunk/PackageAvailabilityServiceTest/common@RR[none => 62657_2011/04/19 09:37:54 +0100]@a761a411-749e-40ff-9a2d-29ba3934af2b
jetbrains.buildServer.agent.impl.patch.PatchDownloaderImpl$1: Server was not able to build correct patch, most likely due to VCS errors, will try again.
at jetbrains.buildServer.agent.impl.patch.PatchDownloaderImpl.throwError(PatchDownloaderImpl.java:113)
at jetbrains.buildServer.agent.impl.patch.PatchDownloaderImpl.checkPatch(PatchDownloaderImpl.java:103)
at jetbrains.buildServer.agent.impl.patch.PatchDownloaderImpl.copyPatchAndCheck(PatchDownloaderImpl.java:64)
at jetbrains.buildServer.agent.impl.patch.UpdateSourcesPatcherBase.copyPatchToTempFile(UpdateSourcesPatcherBase.java:70)


Caused by: jetbrains.buildServer.vcs.patches.UnsuccessfulPatchException: Failed to build patch for build #18 {build id=197}, VCS root: svn: http://canary.saga.co.uk:81/svn/TheVault/Taurus/trunk {id=2}, due to error: Unknown path kind: none for http://canary.saga.co.uk:81/svn/TheVault/Taurus/trunk/PackageAvailabilityServiceTest/common@RR[none => 62657_2011/04/19 09:37:54 +0100]@a761a411-749e-40ff-9a2d-29ba3934af2b
at jetbrains.buildServer.vcs.patches.AbstractPatcher$1.fail(AbstractPatcher.java:93)
at jetbrains.buildServer.vcs.patches.LowLevelPatcher.readPatchStream(LowLevelPatcher.java:156)
at jetbrains.buildServer.vcs.patches.LowLevelPatcher.applyPatch(LowLevelPatcher.java:79)



I've tried a number of ways to get this to work including forcing clean builds, deleting the server cache folder, but none seemed to make any difference.


We're using 6.0.1 (build 15816) .

Many Thanks,
Mike S.

2 comments
Comment actions Permalink

Hi Mike

Could you also post teamcity-vcs.log please.

Thanks

0
Comment actions Permalink

I had this problem too, when renaming the SVN VCS root directory. I solved it by deleting and re-creating the VCS root. (And also deleted the local TC agent work directory for that build configuration, not sure that made any difference but it didn't hurt).

I think it was caused by TeamCity attempting to get the list of changes using the old revision number combined with the new path (which didn't exist in the old revision).

For example:

svn/myapp_oldname/trunk r100
svn/myapp_newname/trunk r101

and TeamCity tries to get changes of svn/myapp_newname/trunk starting from r100 which is an error because it didn't exist yet.

0

Please sign in to leave a comment.