Cannot checkout from SVN

Hi,

I am trying to setup TeamCity 2.0. When I run a build, I get the following error:

svn: http://ksdev1:8888/repos/ksportal/factory-portal/trunk/
svn: REPORT of '/repos/ksportal/!svn/vcc/default': 400 Bad Request (http://ksdev1:8888/)
jetbrains.buildServer.vcs.VcsException: Cannot request dated revision from svn: svn: REPORT of '/repos/ksportal/!svn/vcc/default': 400 Bad Request (http://ksdev1:8888/)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnConnection.getRevision(SvnConnection.java:175)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnConnection.getEntries(SvnConnection.java:82)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnConnection.addChanges(SvnConnection.java:178)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnSupport.collectBuildChanges(SvnSupport.java:84)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.loadChanges(VcsChangesLoader.java:25)
at jetbrains.buildServer.serverSide.impl.ProjectImpl.loadChanges(ProjectImpl.java:40)
at jetbrains.buildServer.serverSide.impl.BuildStarter$2.run(BuildStarter.java:10)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.tmatesoft.svn.core.SVNException: svn: REPORT of '/repos/ksportal/!svn/vcc/default': 400 Bad Request (http://ksdev1:8888/)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:49)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getDatedRevision(DAVRepository.java:168)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnConnection.getRevision(SvnConnection.java:101)
... 7 more
org.tmatesoft.svn.core.SVNException: svn: REPORT of '/repos/ksportal/!svn/vcc/default': 400 Bad Request (http://ksdev1:8888/)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:49)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getDatedRevision(DAVRepository.java:168)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnConnection.getRevision(SvnConnection.java:101)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnConnection.getEntries(SvnConnection.java:82)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnConnection.addChanges(SvnConnection.java:178)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnSupport.collectBuildChanges(SvnSupport.java:84)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.loadChanges(VcsChangesLoader.java:25)
at jetbrains.buildServer.serverSide.impl.ProjectImpl.loadChanges(ProjectImpl.java:40)
at jetbrains.buildServer.serverSide.impl.BuildStarter$2.run(BuildStarter.java:10)
at java.lang.Thread.run(Thread.java:595)

Does anyone know what the problem is? The checkout works fine under command line.

Many thanks!

Kenny

0
5 comments
Avatar
Permanently deleted user

Hello Kenny,

>svn: REPORT of '/repos/ksportal/!svn/vcc/default': 400 Bad Request (http://ksdev1:8888/)
The most possible reason is proxy misconfiguration.

Taking in account that your command line client works fine, please check the following:

1. Do you have proxy set up for your command line client (%USER_HOME%\Application Data\Subversion\servers on Windows or ~/.subversion/servers on Linux)? If there are proxy settings, please use the same for TeamCity. You may define configuration directory TeamCity will use in TeamCity project VCS root configuration, by default it uses those of the user that runs TeamCity, and this account may be not the one that you use when running command line client.

2. Do you use the same protocol when using command line client? If you're using https (http over SSL), then it makes sense to use https in TeamCity VCS root as well. The reason why http may not work is again proxy configuration that may filter out DAV-specific request that are sent by Subversion client. Of course, it couldn't do filtering when SSL is used. You may find more on proxy setup at http://subversion.tigris.org/faq.html#proxy

Please note, that proxy could be explicitly set (and thus have to be configured) or it could be transparent one, and filter all HTTP requests.

3. Another rare possible reason is that your proxy server allows only certain clients to send HTTP request through it, i.e. web browser and native subversion client. Do distinguish one from another it uses HTTP "User-Agent" header. If it is the case you may need to contact your system administrator to change proxy configuration.

If above will not help, please provide more details on the problem - do you run TeamCity and command line Subversion client on the same computer? Do you have proxy server set up?

Thanks,
Alexander Kitaev.

0
Avatar
Permanently deleted user

Hi Alexander,

Thanks for your reply. We are not using any proxy server and same protocol is used for command line and teamcity. It is strange that this only happens in teamcity. We can checkout the codes in IDEA, Eclipse, Maven, and Continuum without any problems.

Any other suggestions? Thanks much!

Kenny

0
Avatar
Permanently deleted user

Hello Kenny,

Proxy server may be transparent, i.e. it could act as a firewall processing all HTTP requests. I have no ideas about what else could cause the problem so far.

Please, if possible provide more information on your environment:

- Is TeamCity server ran on the same computer that your IDE or on the dedicate one?
- In case it is ran on the same computer, please check that it is ran on behalf of the same user's account as you running your IDE with.
- Please enable debug logging for SVNKit in TeamCity server:
uncomment

]]>

in teamcity-server-log4j.xml file.

Log will contain more information on what was received from the server, and this could help to understand the reason of the problem.

Thanks,
Alexander Kitaev.

0
Avatar
Permanently deleted user

Kenny, if you are running subversion under apache 2.0 (i think that's the only way), try this:

1. edit /etc/httpd/conf.d/mod_security.conf
2. find and comment out line:
Include modsecurity.d/modsecurity_crs_10_config.conf

0
Avatar
Permanently deleted user

I am experiencing the same problem. I enabled debugging, but it didn't reveal anything new.

I am able to check out the source on the same machine running Teamcity with the same username/password. No proxy. Any other ideas?

0

Please sign in to leave a comment.