Problems with svn checkout for password when starting unattended in TeamCity

Question

I am currently setting up StatSVN to run in TeamCity and I am having a problem. I need a little idea. First, StatSVN needs to be run against the working directory that was extracted from SVN; it cannot work against a copy of the application that TeamCity exports from SVN. Therefore, it should perform svn check on the build server.

I created a bat file that runs the three commands that StatSVN needs to create a report, the first of which is checkout:

svn checkout [repository path]

Now, correct me if I am wrong, but this should verify using the current identity. Of course, it works fine right from the command line. When it launches in TeamCity, the build runner is configured to run under a service pack that has the same rights for me in SVN. In fact, the same service account is used to create default repositories and directory structures, so I have no doubt that it has rights.

However, every time the assembly starts, it freezes, and after stopping it is obvious:

[13:38:28]: C:\TeamCity\buildAgent\work\e8d4dc4070ecf602>svn checkout [repository path] 
[13:38:29]: Authentication realm: <[svn server]> Subversion Repositories
[13:38:38]: Password for '[service account]': 
[13:38:38]: Process exited with code 1

It seems that he is hanging and waiting for a password that he clearly cannot get when working without supervision. Anyone have any ideas on why this is happening?

Update: , StatSVN, "svn log", . svn, TeamCity VCS " ", , (, , ), "svn log" - .

Answer 1

svn checkout --non-interactive

, , ,

Answer 2

, teamcity " " (), (checkout)..? svn-.

(nant msbuild), .

, , .

Answer 3

It may be too late to help the OP, but I had a similar problem when doing the checks. svnwill constantly ask for a username and password, despite the fact that they are supplied using the --usernameand switches --password. When a switch was added --non-interactive(as suggested by Sander Rijken), he svnreplied that the password was incorrect. In fact, the password was correct, but contained characters that were not properly escaped.