Failed to perform checkout on agent: svn: E200030: Error during update
Answered
Hi
We are evaluating TeamCity and hope to use it.
TeamCity 2017.1.1 (build 46654), effective release date 2017-Apr-10, currently running in the professional mode.
However, we are having issues with subversion. The build agent is creating the subversion working directory but it is not checking out the files. The generated folder contains the .svn subfolder and that is it. If I use TortoiseSVN on that directory, selecting SVN update, it works just fine.
I have tried extending the time to run the checkout, deleting the generated directory, rebooting etc.
The build log is: (from a time where I deleted d58... folder before running again.
[09:43:54]Will perform clean checkout. Reason: Checkout directory is empty or doesn't exist
[09:43:54]Checkout directory: C:\BuildAgent\work\d58a49672897e277
[09:43:54]Updating sources: auto checkout (on agent) (26s)
[09:43:54][Updating sources] Will use agent side checkout
[09:43:54][Updating sources] VCS Root: code (26s)
[09:43:54][VCS Root: code] revision: 1163_2017/06/02 09:42:02 -0400
[09:43:54][VCS Root: code] Checkout from https://<url>/svn/code/branches/rewrite
[09:43:54][VCS Root: code] Using working copy format 1.8
[09:44:20][Updating sources] Failed to perform checkout on agent: svn: E200030: Error during update from https://<url>/svn/code/branches/rewrite to C:\BuildAgent\work\d58a49672897e277
TortoiseSVN 1.9.5, Build 27581 - 64 Bit , 2016/11/26 09:18:58
Subversion 1.9.5, -release
Subversion 1.9.5, -release
thanks!
Tim
Please sign in to leave a comment.
Hello Tim,
Sorry for the problem. Could you please take a look at this issue: https://youtrack.jetbrains.com/issue/TW-49325
Is the error message in this issue matches the one you faced?
If it is, could you please vote for the issue to watch it, and provide all logs from buildAgent/logs directory as an attachment (you can mark the attachment visible to TeamCity developers only)
Thanks!
Thanks for the possible solution, Kirill. However, I don't think the problem is the same. I don't get a message about unfinished transactions.
I did change the configuration to checkout on the server not agent. I am exploring TeamCity so running it as localhost with server and agent on the same machine. I don't know why but it started working. When I installed TeamCity on a server machine, checking out as a agent worked fine. So far everything is now good. I don't know why, still getting used to agents coming from Jenkins.
Tim
Hello Tim,
I'm glad it works for you finally :)
Good luck with your builds,
KIR
Unfortunately, this problem has reared its ugly head again.
I installed TeamCity Professional on another computer. Setup a project and all was fine. I was using defaults for most things.
Then I set triggers to build the projects in the evening after work. The next day I noticed it failed with the same error as before (OP topic)
Failed to perform checkout on agent: svn: E200030: Error during update from https://svn/code/branches/test to C:\TeamCity\buildAgent\work\d58a49672897e277
I tried to run one of the projects and it failed immediately with the same error. It was working the previous day. I did not make any changes. I looked at the agent work folder. The GUID folder was there but was empty except for .svn. One of the triggers was set to clean. Does it clean everything? I was hoping that it would just remove all files not checked in. Maybe when the folder is empty, TeamCity running svn can't checkout?
If I change the "Prefer to checkout files as agent" to "Always checkout files on server", then running the build works. If I change back to "Prefer to checkout files as agent" then it does not work. If I delete the GUID working folder, it recreates it and still fails when set to "Prefer".
Am I doing something wrong? Why does "Prefer to checkout files as agent" work for me for the first day but then fails? Is it a problem to use "Always checkout files on server?"
Both TeamCity server and agent are running on the same machine.
Windows Server 2012 R2, version 6.3
TeamCity 2017.1.2 (build 46812), effective release date 2017-Apr-10, currently running in the professional mode.
Thanks
Tim
Hello Tim,
Could you please create a corresponding issue in our tracker and attach all logs from buildAgent/logs directory there?
Thanks!