> One of the aspects of and is that they dont print out enough
> useful info on failure. That is partly for security reasons -you dont
> want your entire organisation to be able to read the password in the
> cruise control logs. At the same time, we could do a lot to improve the
> diagnostics tha
Michael Giroux wrote:
Thought you might like to know -- the problem turns out to be user
error. I was watching the developer use the script, and I assumed
that when he entered the password for the target useid, that he had
configured the script to use the userid associated w/ the password.
As it
Thought you might like to know -- the problem turns out to be user
error. I was watching the developer use the script, and I assumed
that when he entered the password for the target useid, that he had
configured the script to use the userid associated w/ the password.
As it turns out, he was takin
I personally do not use passphrase, but I'm not sure what the other
developer is using on his system (the one having problems). I'll
check on Monday.
Thanks
Michael
On 9/29/07, Vihan Pandey <[EMAIL PROTECTED]> wrote:
> > I'm using and tasks in a build script. These work
> > well from my own
> I'm using and tasks in a build script. These work
> well from my own PC, but when someone tries to run the script from a
> different computer, the script fails with an authentication error.
>
> I have been using and for so long, I no longer
> remember what I did to resolve this issue when I
I'm using and tasks in a build script. These work
well from my own PC, but when someone tries to run the script from a
different computer, the script fails with an authentication error.
I have been using and for so long, I no longer
remember what I did to resolve this issue when I had it.
We
