Error: Connecting bamboo to SVN through svnserve

[ryan harvey]

I'm creating a new plan to access a subversion repository, which is managed by svnserve (v1.6.9) instead of an apache-based server (this is pretty common now). The URL for my repository managed by svnserve is "svn://serverlocation/repo/trunk" but when I add that to the Repositopry URL field, I get this error message: This is not a valid Subversion Repository: svn: connection refused by the server.

The Repository URL field on the Create Plan page gives an example path of "http://svn.collab.net/repos/svn/trunk" which is typical for traditional apache servers, but there are 5 different types of svn URL types. Is the "SVN://" path not supported?

I'm able to access this repository via tortoisesvn, command line, etc. so I'm thinking the issue is with bamboo, but there's no activity registering on my repository when I attempt to connect with bamboo. I've tried this with/without login info, with/without a :3690 port declaration on the end of the URL.

Bamboo is able to connect to my Git repositories no problem. Please help!

Background info:
svnserve: http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-serversetup-svnserve.html
svn URL types: http://svnbook.red-bean.com/en/1.2/svn.basic.in-action.html#svn.basic.in-action.wc.tbl-1

[ryan harvey · Accepted solution]

Problem: operator error. Repository URL was incorrect. But I wasn't prepared to press our sysadmin about it until I was sure SVNSERVE was supported. Maybe an explicit note or example in the documentation? Not necessary, but could help someone avoid my problem in the future. Thanks, Przemek and Piotr!

[Piotr Stefan Stefaniak [Atlassian]]

Bamboo supports the "SVN://" path - at least I'm able to access my test svn repository via SVN:// protocol. Which Bamboo version are you using?

[Przemyslaw Bruski]

Which Bamboo version are you using?

[ryan harvey]

I'm using this Bamboo v 3.2, this is the SVN path: svn://generic.host.name.com/var/svn-repos/hda/trunk

[Przemyslaw Bruski]

Hmm, you have the latest version - as Piotr said: it should work, please contact support (http://support.atlassian.com), we will be able to assist you with solving this problem.