On Mon, Aug 23, 2021 at 02:45:44PM +0200, Johan Corveleyn wrote: > Thanks, those are good efforts (and thanks to both Daniels for writing > them), but I'm afraid those workarounds are not good enough. The thing > is: this is not for me alone. This needs to be handled in buildscripts > that can be run by around 50 developers.
One thing is unclear to me: At some point, someone has to run an svn command to get the passward cached on Solaris in the first place or build scripts would be failing. How is this done? Each of the 50 developers ran 'svn checkout' or something similar to get the password cached? Or does the password get cached in a non-interactive, automated way? The point of this question is to understand whether my 'svn auth add' proposal described elsewhere in this thread would solve your problem.
