SVN update fails

let me first report that the newest TeamCity EAP is running nicely here, and yet no further occurances of the "severe SVN problem, using wrong branch" did happen.

there seems to be a new, annoying problem:
repeatedly TeamCity fails to perform the svn update, as it seems.
The symptoms are like this. Example:
in a java project you have compilation failed because one variable is private and you did not check the file in where the variable was changed to public.
ok, you do check in the relevant file now, and TC starts to build shortly after.
For this build, it lists our relevant checkin in the changes view.
But...the compilation fails, still complaining about the private variable!

looking on the filesystem of the server: yes, the file has not been updated.

build agent log says:
INFO - jetbrains.buildServer.AGENT - Getting sources...
INFO - jetbrains.buildServer.AGENT - Requesting patch from server, cleanPatch=false
INFO - jetbrains.buildServer.AGENT - Copying patch to temp file...
INFO - jetbrains.buildServer.AGENT - Patch downloaded
INFO - jetbrains.buildServer.AGENT - Sources loaded for 0 seconds
INFO - jetbrains.buildServer.AGENT - Patch applied successfully
INFO - jetbrains.buildServer.AGENT - Patch applied for build 75367

can this be a time sync problem between tc and svn server?

Comment actions Permalink

Michael, did TeamCity server detect the change in the build? Could you see the change on the web for build with old file?

Comment actions Permalink

TeamCity server did detect that something was committed and because auf "VCS triggered build" it therefore started building.
The change was listed in the web UI "changes" view.
But the change was not on the filesystem of the server.

Comment actions Permalink

Please create new JIRA issue, attach there logs from the agent and TeamCity server. Also check please if vcs root revision (on the build result changes page) shows the right repository version (for the build).
Is the problem reproducable?


Please sign in to leave a comment.