On Sep 13, 2010, at 06:05, Zvika Haramaty wrote:
> Problem:
> • We’re using large components, each built of dozens of SVN repositories.
> • Checking out such a component can take 6 hours (we call this operation ‘populate’).
> • I.e., we want the populate to be as much automatic as possible.
> • Our IT department requires us to change password every few months.
> • Every time the password is changed, the populate procedure stops for several times, requesting for the new password.
> • Of course, there is local caching for ‘known password’s. However, updating password is a nightmare.
>
> Possible solution:
> • The password can be saved to a special environment setting (e.g. SVN_PASSWORD)
> • The password can be stored in the ~/.subversiom/.auto directory -
> Not caching after user has written the password; but storing the password beforehand.
Have you considered using Subversion's existing --username, --password and --no-auth-cache arguments?
Received on 2010-09-13 13:20:41 CEST