In case anyone else runs into this, I found that specifying environment
variables for the slave allowed me to set HOME and put the ssh keys &
config there. This appears to mostly be working now (with the exception of
submodules, but that's another issue)

On Mon, May 13, 2013 at 8:01 AM, Chanda Unmack <[email protected]> wrote:

> Our gerrit server was upgraded this weekend and have run into a snag on
> our windows slaves. I am able to do a git clone on the slaves as the user
> the jenkins service is running as, but as soon as I try within a job, it
> just hangs. I mucked with the known_hosts and all that did was change it
> from hanging to complaining that the key was invalid. I know the key is
> fine as I tested it with ssh -i <key> -p 29418 user@gerrit as well as
> cloned repos from the command line, but I am not sure it's in the right
> place. I have copied the key and known_hosts to the fs root for the slave,
> the home directory of the user jenkins is running as, the local system
> account (C:\Windows\SysWOW64\config\systemprofile), and the git directory
> (all suggestions from google search results). I set permissions for the
> .ssh directory and all it's contents to be the local system account, still
> hangs. I set the permissions to be the user the jenkins service is running
> as, still hangs. I've run out of ideas as to where jenkins is looking for
> the ssh keys.
>
> I should point out that the linux and osx slaves have no issue cloning
> from the new gerrit server, and I have tried copying the keys to one of
> those working slaves and it had no problem cloning.
> I'm really hoping that it's just something glaringly obvious that I'm
> missing
>
> Jenkins version 1.480.2
> Gerrit version 2.5.2
> Git plugin version 1.2.0
> Gerrit Trigger plugin version 2.9.0
>
> thanks!
> chanda
> --
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to