Hi Ram,
Yes, cloning from the command line works fine in all the instances.
We can also get around the issue by creating a credential in Jenkins using the
private key of the user, but for some reason the Public Key no longer works.
Thanks,
John
On Mar 4, 2018, at 1:31 AM, Ramanathan Muthaiah
>
> Here are the errors we are running into (Credentials *Unix BitBucket
> Groovy* are the name of the credentials commonly used across all
> platforms):
>
>
>
> Building remotely on *XXXJENKINSNODEXXX* in workspace
> d:\scm\checkout\John-Test
>
> > D:\SCM\Apps\Git\2.8.2\bin\git.exe rev-par
Hi All,
I have seen a few write-ups about this and just want to get some clarification,
as I have not been able to solve this as of yet in our environments.
We are using Jenkins Master v2.89.4 on Windows 2008 R2 Servers. We have the
latest Git (3.8.0) & Git Client (2.7.1) plugins installed.
We
