21.05.2013 00:09, Chanda Unmack kirjoitti:
On Mon, May 20, 2013 at 12:38 PM, Alex Grönholm
mailto:alex.gronh...@nextday.fi>> wrote:
20.05.2013 19:03, Chanda Unmack kirjoitti:
I had a similar situation with git - I found the best way to see
what's going on is to set up a test jo
On Mon, May 20, 2013 at 12:38 PM, Alex Grönholm wrote:
> 20.05.2013 19:03, Chanda Unmack kirjoitti:
>
> I had a similar situation with git - I found the best way to see what's
> going on is to set up a test job that does a ssh -vvv to the git server
> (Mercurial in your case)
> That showed me whi
20.05.2013 19:03, Chanda Unmack kirjoitti:
I had a similar situation with git - I found the best way to see
what's going on is to set up a test job that does a ssh -vvv to the
git server (Mercurial in your case)
That showed me which keys it was using and whether or not it actually
used the .ssh
20.05.2013 19:03, Chanda Unmack kirjoitti:
I had a similar situation with git - I found the best way to see
what's going on is to set up a test job that does a ssh -vvv to the
git server (Mercurial in your case)
That showed me which keys it was using and whether or not it actually
used the .ssh
I had a similar situation with git - I found the best way to see what's
going on is to set up a test job that does a ssh -vvv to the git server
(Mercurial in your case)
That showed me which keys it was using and whether or not it actually used
the .ssh/config file
hth
chanda
On Sat, May 18, 2013
I have a Jenkins installation on a Linux box and a Windows 7 build slave
for building Windows-only projects. Trouble is, I can't get the slave to
check out the source repository with Mercurial. It always hangs, possibly
due to SSH waiting for password input even though it's running in a
headles
