Hi.

 
Problem:

1.      We're using large components, each built of dozens of SVN
repositories.
2.      Checking out such a component can take 6 hours (we call this
operation 'populate'). 
3.      I.e., we want the populate to be as much automatic as possible.
4.      Our IT department requires us to change password every few
months.
5.      Every time the password is changed, the populate procedure stops
for several times, requesting for the new password.
6.      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.

 

Thanks,

Zvika

 

 

Reply via email to