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 <rus.cah...@gmail.com<mailto:rus.cah...@gmail.com>> wrote: Have you tried running, manually from command line, 'git clone' using the creds in the problematic nodes ? /Ram ________________________________ [https://www.aciworldwide.com/-/media/aci-footer]<http://www.aciworldwide.com> This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0F3A6A17-DC54-48D0-B2A7-5E8E7C333771%40aciworldwide.com. For more options, visit https://groups.google.com/d/optout.
