VCS errors: how to figure the error and fix?

Here's a chunk of the Teamcity log file:

[14:02:51]: Updating sources: server side checkout...
[14:02:51]: [Updating sources: server side checkout...] Will perform clean checkout. Reason: Agent doesn't have any version of the project sources
[14:02:51]: [Updating sources: server side checkout...] Building clean patch for VCS root: scgui _code
[14:02:52]: [Updating sources: server side checkout...] Failed to build patch for build 26 {build id=26}, VCS root: svn: https://f<svn server/repositoryname>/ {id=1}, due to error: Unknown path kind: none for https://<svn server/repositoryname>/trunk/<projectname>/code@RR[ null => 109_2010/04/28 14:08:48 -0700@69681eab-4427-4e63-a8f7-7d6f7b959077 ]
[14:02:52]: [Updating sources: server side checkout...] Repository sources transferred
[14:02:52]: Patch is broken, can be found in file: C:\TeamCity\buildAgent\temp\cache\temp3313387897271619847patch_26
[14:02:52]: RunBuildException when running build stage UpdateSourcesFromServer: Failed to build patch for build 26 {build id=26}, VCS root: svn: https://<svn server/repositoryname>/ {id=1}, due to error: Unknown path kind: none for https://<svn server/repositoryname>/trunk/<projectname>/code@RR[ null => 109_2010/04/28 14:08:48 -0700@69681eab-4427-4e63-a8f7-7d6f7b959077 ]
[14:02:52]: jetbrains.buildServer.agent.impl.patch.PatchDownloaderImpl$1: Server was not able to build correct patch, most likely due to VCS errors, will try again. jetbrains.buildServer.agent.impl.patch.PatchDownloaderImpl$1: Server was not able to build correct patch, most likely due to VCS errors, will try again.

I've set up a VCS root, and the test button works successfully. TortoiseSVN is installed on the server that has the TeamCity Server and Agent.

Do we need to install SVN itself on this server?

How do we figure out what "Unknown path kind" means?

Thanks,
Marcel

12 comments

Hello Marcel,

  This error message means that TeamCity is unable to determine the type of the file for the given path. The most possible reason
  is that specified path doesn't exist on SVN server.

  Whether "Test connection" command works on the VCS settings screen?
  Can you attach teamcity-vcs.log log file from TeamCity/logs directory?

  Regards,
  KIR

0

Hi KIR,

Here's the file.

Clicking "test connection" on the Edit VCS Root page says "Connection successful"  

Thanks,
Marcel



Attachment(s):
teamcity-vcs.log.zip
0

Is it possible that TeamCity's connection is somehow case sensitive?

If I test the connection with https://<svn server>/<repo name>/trunk/<project name>/code, Test Connection fails.

If I test with https://<svn server>/<repo name>/trunk/<project name>/Code, Test Connection works.

However, I can't set the '/trunk/<project name>/Code' part of the url in the VCS because that's coming from somewhere else. I'm not sure where, but maybe the SVN files in the checkout directory? The reason I guess that is that if I add that chunk onto the url in the VCS Root, the error lists this path:

https://<svn server>/<repo name>/trunk/<project name>/Code/trunk/<project name>/code

0

Hello Marcel,

  Are there a chance you're using  checkout rules and these checkout rules contain path in incorrect case?
   The checkout rules are specified at the VCS settings screen for build configuration (Step 2).

  Regards,
  KIR

0

Yes, there is path information in the checkout rule.

If I remove the checkout rule, will it still do an svn update on the source directory?

Thanks,
Marcel

0

One other thing I should probably mention is that source folders for this project are large (1.5GB) and doing a full checkout takes about 5 hours, so I'm trying to set it up using an existing SVN working copy. I was also hoping to add a checkout rule to ignore the subfolder with the large static content files.

I removed all checkout rules, and hit Run. It's still running after 10 min but no error messages.

0

Hello Marcel,

  I thought you had an error in your checkout rules where you specified 'code' instead of 'Code'.
  And this could be the reason for the error.

  Regards,
  KIR

0

Hello KIR,

It could be.

I've changed the checkout folder to a new separate folder instead of the existing code folder, added a check rule to ignore the main static content folder with all the large files '-:Code/Content'

I've attached the log output when I try to run it, since I can't figure out how to paste into this text editor.

In any case, this seems to be the point that TeamCity hangs up. I've left it running for up to 30 min at this stage.

It's currently set to Server Side Checkout, so if TC is trying to do a check out some where, then it'll be working on that for the next 5 hours or so. How do I find out what TC is doing at this point?

What happens if I set it to Agent checkout? or to not checkout automatically?

Thanks,
Marcel



Attachment(s):
TeamCityLogOutput.rtf
0

Hello Marcel,

  I don't think TeamCity hangs up. I think it is busy checkouting your sources on the server side and preparing a patch to send to agent.
  Given that you have a large volume of sources, it will take quite some time.

  I think the best solution in your case would be to use agent-side checkout and do not add exclude pattern at all.
  After the first initial long checkout, subsequent checkouts should work much faster.

  Kind regards,
  KIR

0

Svn is case sensitive.  It isn't TeamCity in that case, it's svn.  We switched to it from StarTeam while we were still using CruiseControl and that little "feature" nearly killed us.  If you don't get the case right in your checkout rules, that will cause errors too.

0

Hello KIR,

It's working now. I added a checkout rule to ignore the static content folders, which enabled the build job to complete.

Thanks for the help.

0

Yes, it's true that it's SVN in this case that was causing the problem, but since TortoiseSVN is not case sensitive, we have never had an issue with case sensitivity using SVN, so it wasn't easy to figure out because we weren't aware of it. It's a baffling problem if you're not use to command line SVN. We got Hudson up and running at the same time we were trying to figure this one out.

Actually, if TeamCity just put a caveat / reminder about case sensitivity on the examples / help text for the textboxes for the urls, we might have figured it out a lot sooner.

cheers,
Marcel

0

Please sign in to leave a comment.