Unfortunately, --non-interactive appears to be ignored as well. My URL
is of the form
svn+ssh://server_name/path/to/repos
Could SSH be doing something under the hood (like forcing interactive
authentication)?
On Thu, 2007-08-16 at 23:36 +0200, Erik Huelsmann wrote:
> On 8/16/07, Steve Perry <steve.perry@makotoconsultinggroup.com> wrote:
> >
> > I'm running svn client 1.4.2 (r22196) and it appears that when I pass the
> > --password option to svn (if I'm, say, doing a log to see what's changed) I
> > am prompted for a password anyway. Normally, I wouldn't grumble about this,
> > but I am using the svn client with Cruise Control, so this is going to be a
> > problem... It is definitely the svn client, though (and not Cruise). When
> > running as, say, user cruise, I type:
> >
> > svn --password foo log whatever/myproject
> >
> > I am still prompted for a password. No dice either when I try:
> >
> > svn --username cruise --password foo whatever/myproject
> >
> > (even though, like I said, I'm running as user cruise). ** Other than
> > needing to interactively enter the password in order for the command (and
> > any other command I've tried, btw, such as checkout) to succeed, it works
> > fine. ** Anyone ever run into this? This is really putting a damper on my
> > Cruise Control mojo... Thanks for any (useful) help.
>
> Does it work when you pass --non-interactive?
>
> bye,
>
> Erik.
>
>
Received on Thu Aug 16 23:49:19 2007