[Buildbot-devel] Buildbot workdir issues

[Brian Warner]

> This is an internal project for which we have to limit access, unfortunately.

But the SVN server is still accessible to the world? (i.e., everybody can get
as far as presenting a password (maybe even in plaintext??) to the
repository).

So far, most of the closed repositories I've run across are either
unrestricted but inside a firewall, or world-visible but only through ssh. In
the latter cases, I usually give the buildslave a passphraseless ssh private
key and put the matching public key in a ~buildslave/.ssh/authorized_keys on
the repository side. Either that or, when you start the buildslave, start it
in an environment with an ssh-agent running and the suitable key unlocked.

If I remember right, CVS will cache the username/password information in a
shared place like ~/.cvspass, which means you can do a CVS operation
manually, once, and then later on the buildslave will be able to take
advantage of the cached credentials. Perhaps there is a way to get SVN to do
the same thing, cache it outside the tree (which could get blown away
sometimes)?

cheers,
 -Brian