Thank you for the advice Mark. I would be fine using 'git clone', except I hate missing the "*Recent Changes*' that I believe was generated because I used the Jenkins git plugin.
I will keep working on it. Thanks again. -Ed On Tuesday, January 21, 2020 at 3:12:32 PM UTC-6, Mark Waite wrote: > > > On Tue, Jan 21, 2020 at 10:24 AM Eddie Sutton <[email protected] > <javascript:>> wrote: > >> *What I Tried:* >> >> 1) Set *Source Code Management > GIT > Repository URL* to: >> >> [email protected]:v3/acmeinc/my-app/my-app >> >> Failed to connect to repository : Command "git ls-remote -h -- >> [email protected]:v3/acmeinc/my-app/my-app HEAD" returned >> status code 128: >> stdout: >> stderr: Host key verification failed. >> fatal: Could not read from remote repository. >> >> > That message is a "permission denied" message. It could be for many > different reasons, possibly including: > > 1. Failed to provide a private key credential in the Jenkins job > definition. Use the Jenkins credentials plugin to add the private key > which has also been registered with visualstudio.com > 2. Failed to register the public key with visualstudio.com. Add the > public key from the private key credential to the repository on > visualstudio.com > 3. Used an outdated command line git version. Use a recent command > line git version instead > 4. Used command line git from cygwin instead of using git for > windows. The git plugin is not tested with cygwin. It is tested > frequently with recent releases of git for windows. Use git for windows > instead of cygwin > > > >> *Work-Around* >> >> My work-around was to change job to use a bash shell. >> >> However, I very much miss the "*Recent Changes*" section that was >> displayed in my job previously. >> >> I *think* the "*Recent Changes*" were generated from the GIT Plugin. >> >> >> >> echo "git clone using public SSH key of build slave..." >> echo "Works but no 'Recent Changes' section for your job" >> git clone [email protected]:v3/acmeinc/my-app/my-app . >> >> Thanks in advance for any tips or suggestions, >> >> > You're welcome to use your own 'git clone' inside the job definition, > though that removes many of the things that Jenkins could do for you and > makes it more difficult for you to use additional agents. Each agent will > need the same private key credentials. > > > >> -Ed >> >> >> >> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/CAKas9SQ8MdJud0Wsu6tR8%3DvkeYevVrZseMyYuUWMNfYqsvRxFA%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/CAKas9SQ8MdJud0Wsu6tR8%3DvkeYevVrZseMyYuUWMNfYqsvRxFA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > Thanks! > Mark Waite > -- 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/492fe750-2014-4958-b145-3fc69cbcb3fc%40googlegroups.com.
