RE: svn????????

> I would rather have to change the password that my build server uses
> every x months than have to manually do a build every x days or hours.

We only do this for "release builds" (weekly), not for our CI builds (hourly). For the CI builds there is no problem because they don't need write access to SVN (just checkout latest version and build it).

For the weekly release build, "manually" will boil down to:
$ ssh buildmachine
Password: ********
buildmachine $ doIt
[... lots of output of the build process, if you like ...]
buildmachine $ logout

But you're right, it's still some "manual developer time" that's being used (only to provide credentials to authenticate to SVN).

On the other hand, changing the password on the build server every 3 months can be annoying too. And where are you storing that "automation" password (in a secure way)? Or would you just use SVN's client credential caching for this (of the build user's system account)? To change it, you'd have to login with that build user and perform some svn action interactively, so you it can prompt you for the new password...

Nonetheless, thanks for the feedback. I guess I'm just being a little anal-retentive here ...

Johan

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1996277

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-30 17:07:26 CEST