Svn – Subversion user management with LDAP and local users

I have set this up before, and the way subversion works it would prompt you for your passwords hundreds of times during a session.

(To do this, simply connect your subversion client to svn+ssh://username@servername/path/to/repo)

The answer is to use ssh keys.

Set up your private/public key pair, and upload your public key to your ~/.ssh/authorized_keys file, but prefix it with "command="/usr/bin/svnserve -t -r /path/to/repo"

And connect again using svn+ssh as mentioned above

Subversion is a version control system not a deployment system. Don't use it. Since you are doing everything manual right now (building & test) I would also deploy manually, that can also mean that you write some scripts that check the right version out from subversion and deploy it to whatever environment you want it to.

If you want to automate more, I would recommend a CI server or some sort of deployment solution for that. We are starting to use Hudson for testing and deployment (at least for the sandbox environment). We don't intend to use it for production. Because we did not check into the promotion plugin yet. When researching CI servers, I noticed that commercial systems usually offer a better support for release management.