Can you try dumping the environment variables on each node and see if there
are any differences?

On Thu, May 10, 2018 at 10:42 AM red 888 <[email protected]> wrote:

> Super frustrating because this is working on one of my windows slaves, but
> not this one- and I cant find any config differences.
>
> On the working slave I see this:
>
>
> [Pipeline] checkout
> Cloning the remote Git repository
> Cloning repository [email protected]:myteam/myapp.git
>  > git init C:\Jenkins\workspace\test-slave123456 # timeout=10
> Fetching upstream changes from [email protected]:myteam/myapp.git
>  > git --version # timeout=10
> using GIT_SSH to set credentials mygitcreds
>  > git fetch --tags --progress [email protected]:myteam/myapp.git 
> +refs/heads/*:refs/remotes/origin/* # timeout=45
>  > git config remote.origin.url [email protected]:myteam/myapp.git # 
> timeout=10
>  > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
> timeout=10
>  > git config remote.origin.url [email protected]:myteam/myapp.git # 
> timeout=10
> Fetching upstream changes from [email protected]:myteam/myapp.git
> using GIT_SSH to set credentials mygitcreds
>  > git fetch --tags --progress [email protected]:myteam/myapp.git 
> +refs/heads/*:refs/remotes/origin/* # timeout=45
>  > git rev-parse "origin/test-slave^{commit}" # timeout=10
> Checking out Revision 30f11ef09ab13f73fb9a6b75983e1bf32437f51d 
> (origin/test-slave)
> Enabling Git LFS pull
>  > git config core.sparsecheckout # timeout=10
>  > git checkout -f 30f11ef09ab13f73fb9a6b75983e1bf32437f51d # timeout=45
>  > git config --get remote.origin.url # timeout=10
> using GIT_SSH to set credentials mygitcreds
>  > git lfs pull origin # timeout=45
> Commit message: "test slave"
>  > git rev-list --no-walk 30f11ef09ab13f73fb9a6b75983e1bf32437f51d # 
> timeout=10
>
>
>
> But on the failing slave:
>
>
> [Pipeline] checkout
> Cloning the remote Git repository
> Cloning repository [email protected]:myteam/myapp.git
>  > git init C:\Jenkins\workspace\test-slave123456 # timeout=10
> Fetching upstream changes from [email protected]:myteam/myapp.git
>  > git --version # timeout=10
> using GIT_SSH to set credentials mygitcreds
>  > git fetch --tags --progress [email protected]:myteam/myapp.git 
> +refs/heads/*:refs/remotes/origin/* # timeout=45
> ERROR: Error cloning remote repo 'origin'
> hudson.plugins.git.GitException: Command "git fetch --tags --progress 
> [email protected]:myteam/myapp.git +refs/heads/*:refs/remotes/origin/*" 
> returned status code 128:
> stdout:
> stderr: [email protected]: Permission denied (publickey).
> fatal: Could not read from remote repository.
>
>
> Its the same pipeline job, same repo, same creds, and the slave should be
> configured the same but when I change the agent to point to the other slave
> it cant clone.
>
>
> On the working slave all i had to do was install git for windows (turn off
> windows cred store), install java, and then run the jnlp jar.
>
>
> Tried to do the same thing on the non working slave so I dont know why
> that one could be failing.
>
> --
> 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].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/3afe4362-20f7-40c9-91ac-ac6573d0bd16%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/3afe4362-20f7-40c9-91ac-ac6573d0bd16%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVft0hmukqoCu-JQckBpj%3D72CwCfQp_tTwAz5kAvT_-qRg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to