We had our repo set to 'Detect and Checkout'. During repository check we're getting tons of errors in the windows event log:
2016 Apr 01 09:02:46 WinEvtLog: Application: ERROR(0): Continua: (no user): no domain: DevContinua.drbsystems.com: Cannot get changes for repository @link(2002, 1e111a19-0a7e-4324-9be6-8a14ac88e2e2)[Development]: Error running SVN : Running C:\Program Files\CollabNet\Subversion Client\svn.exe with arguments "propget svn:externals https://devsubversion.drbsystems.com/svn/Development/Trunk/PointOfSale/@19697 --non-interactive --trust-server-cert --no-auth-cache --username DevBuildUser ************************* --xml" failed with return code 1 and error output:**********@19697' svn: E200000: A problem occurred; see other errors for details "
when I run the same command from command prompt it returns (not I tried with sliksvn and collab.net svn, both the same):
<?xml version="1.0" encoding="UTF-8"?>
svn: warning: W200017: Property 'svn:externals' not found on 'https://devsubvers
ion.drbsystems.com/svn/Development/Trunk/PointOfSale@19697'
svn: E200000: A problem occurred; see other errors for details
The warning is correct, that particular path never had svn:externals property. However once it starts failing on the above the repository shows good but doesn't have the latest change sets. Resetting the repository does not help.
After changing externals handling from 'Detect and Checkout' to 'Checkout' the problem seems to have resolved. In our case I don't believe we have any externals that reference other repositories, we just pull from other projects and shared locations in the same repo so I believe we're find with 'Checkout'.
I didn't dig very deep into this, it appears to be a bug in CI. Perhaps the svn E200000 'error' is really the culprit, unless that code is supposed to be a warning.
Other suggestions of course appreciated..
HI,
Which version of the svn client are you using? The response we get from this command when the property does not exist is:
<?xml version="1.0" encoding="UTF-8"?><properties>properties>We’ll update to code to deal with the error code that you are seeing.
Note that the difference between “Checkout” and “Detect and Checkout”, is that “Checkout” mode will only detect a new revisions on the main repository. “Detect and Checkout” will also detect changes on the external repository. A build would not be triggered in “Checkout” mode when you add a revision to the external repository.
When we first had the problem we were using sliksvn 1.9.3. I switched to the collab.net version 1.9.3 and get the same output.
We’re using VisualSVN server 3.5.1
Hi,
Thank you for the extra information. We have now reproduced the issue - it was happening only when checking externals on a single folder after detecting that a folder was modified, and only with later versions of svn. We have now updated the code to ignore the warning for the next version.
Excellent… Glad you were able to reproduce!