[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title Mark Waite resolved as Fixed Fixed in git client plugin 2.7.2 released 12 May 2018 Jenkins / JENKINS-50573 Wrong username used for clone with Git 2.17 on Windows Change By: Mark Waite Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-50573 Wrong username used for clone with Git 2.17 on Windows Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50573 Re: Wrong username used for clone with Git 2.17 on Windows Code changed in jenkins User: Mark Waite Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java src/test/java/org/jenkinsci/plugins/gitclient/CredentialsTest.java http://jenkins-ci.org/commit/git-client-plugin/e2520d9a1a52fa210004e9a0d4cea42d97cf9fae Log: JENKINS-50573 Prefer URL username with ssh URL When using an ssh private key, the CliGitAPIImpl implementation previously passed a "-l" command line argument from the username associated with the ssh key. OpenSSH implementations prior to OpenSSH 7.7 would only use that command line argument if no username were included in the ssh URI. OpenSSH 7.7 changes the ssh command line argument parsing rules. Previously, the last user name specified would be used, including the user name in the URL. With OpenSSH 7.7, the first user name specified is used, even if a user name is specified in the URL. The command line: ssh -l jenkins g...@github.com:jenkinsci/git-client-plugin.git uses the username 'git' with OpenSSH versions before 7.7 and uses the username 'jenkins' with OpenSSH 7.7. OpenSSH 7.7 is included in Windows Git 2.17 and in OpenBSD 6.3. The CredentialsTest class can test this case. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title Mark Waite edited a comment on JENKINS-50573 Re: Wrong username used for clone with Git 2.17 on Windows Debain Buster (the testing release) has now updated (at least on the Raspberry Pi where I'm tracking it) to [ OpenSSH 7.7p1 |https://packages.debian.org/buster/openssh-client] and [ git 2.17.0 |https://packages . debian.org/source/buster/git]. That makes this problem even more serious, since it is much more work to switch to a different git version on Linux than on Windows. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title Mark Waite commented on JENKINS-50573 Re: Wrong username used for clone with Git 2.17 on Windows Debain Buster (the testing release) has now updated (at least on the Raspberry Pi where I'm tracking it) to OpenSSH 7.7p1 and git 2.17.0. That makes this problem even more serious, since it is much more work to switch to a different git version on Linux than on Windows. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title Mark Waite edited a comment on JENKINS-50573 Re: Wrong username used for clone with Git 2.17 on Windows The [pull request|https://github.com/jenkinsci/git-client-plugin/pull/309] to fix this needs further interactive testing and regression testing. Download the [build|https://github.com/jenkinsci/git-client-plugin/pull/309] and install it on your machine.Those able to assist with either interactive testing or regression tests should report their results in the [pull request|https://github.com/jenkinsci/git-client-plugin/pull/309]. The workaround technique used by [~lflaherty] is good, since it sets the username associated with the private key credential to be the same as the username that needs to be passed as the login_name argument. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title Mark Waite commented on JENKINS-50573 Re: Wrong username used for clone with Git 2.17 on Windows The pull request to fix this needs further interactive testing and regression testing. Download the build and install it on your machine. Those able to assist with either interactive testing or regression tests should report their results in the pull request. < /td> Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title Lee Flaherty commented on JENKINS-50573 Re: Wrong username used for clone with Git 2.17 on Windows Noticed this with the Blue Ocean generated SSH key after updating a windows slave, the workaround was relatively simple but took a little digging to find. I needed to locate the generated blue ocean-private-key-domain under the admin user which setup the pipeline and change the username to git Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title Lee Flaherty updated an issue Jenkins / JENKINS-50573 Wrong username used for clone with Git 2.17 on Windows Change By: Lee Flaherty Attachment: BlueOceanGeneratedKeyWorkaround.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Mark Waite edited a comment on JENKINS-50573
Re: Wrong username used for clone with Git 2.17 on Windows
OpenSSH 7.7 changed the order of evaluation of login_name. OpenSSH 7.7 is first bundled in Git for Windows 2.17.0. [OpenSSH bug 2385|http://bugzilla.mindrot.org/show_bug.cgi?id=2385] describes the prior order as:{quote}1. user specified before @ character in hostname string 2. login_name specified using -l switch (last value wins) 3. User option provided as a parameter to -o switch 4. User option in matching Host block from per-user config ~/.ssh/config 5. User option in matching Host block from systemwide config /etc/ssh/ssh_config If there is nothing from above specified, username on local terminal is used.{quote}The OpenSSH 7.7 login_name evaluation order is: # login_name specified using -l switch (first value wins) # user specified before @ character in hostname string # User option provided as a parametr to -o switch # User option in matching Host block from per-user config ~/.ssh/config # User option in matching Host block from systemwide config /etc/ssh/ssh_configIf there is nothing from above specified, username on local terminal is used.[OpenSSH Portable bug 2849|http://bugzilla.mindrot.org/show_bug.cgi?id=2849] has been submitted to track the change.Johannes Schindelin of the Git for Windows project has submitted a [pull request|https://github.com/openssh/openssh-portable/pull/91] to the OpenSSH Portable project. The OpenSSH project has closed the [bug report|http://bugzilla.mindrot.org/show_bug.cgi?id=2849] as "Won't Fix". Damien Miller states that the behavior change is intentional.I'll start the work to adjust the git client plugin and/or the git plugin to adapt to the OpenSSH behavior change.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Mark Waite edited a comment on JENKINS-50573
Re: Wrong username used for clone with Git 2.17 on Windows
I've duplicated the problem in my environment. Alternatives include:# Enable JGit in your installation and configure the job to use JGit instead of command line git# Use Windows command line git 2.16.2 or earlierProblem is specific to OpenSSH 7.7 which is included with the Windows version of git 2.17.0. The behavior of the "-l" command line argument changed in the ssh command in OpenSSH 7.7. Previously the last argument value was used and did not override the username in the connection string ("URI"). Now the first argument value is used and it overrides the username in the connection string. The same problem is likely visible with OpenBSD 6.3, the first version that includes OpenSSH 7.7.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Mark Waite edited a comment on JENKINS-50573
Re: Wrong username used for clone with Git 2.17 on Windows
I've duplicated the problem in my environment. Alternatives include:# Enable JGit in your installation and configure the job to use JGit instead of command line git# Use Windows command line git 2.16.2 or earlier I'll start a conversation with the git for windows team to understand what may have changed in the handling of GIT_SSH authentication settings. The git plugin may need to be updated to follow the technique recommended in JENKINS-32883 if it detects a modern enough version of command line git. Problem appears to be is specific to OpenSSH 7.7 which is included with the Windows version of git 2.17.0. I compiled git 2 The behavior of the "-l" command line argument changed in the ssh command in OpenSSH 7 . 17 7 . 0 on Ubuntu 16.04 Previously the last argument value was used and did not override the username in the connection string ("URI"). Now the first argument value is used and it successfully with overrides the Jenkins git plugin username in the connection string .
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Mark Waite edited a comment on JENKINS-50573
Re: Wrong username used for clone with Git 2.17 on Windows
OpenSSH 7.7 changed the order of evaluation of login_name. OpenSSH 7.7 is first bundled in Git for Windows 2.17.0. [OpenSSH bug 2385|http://bugzilla.mindrot.org/show_bug.cgi?id=2385] describes the prior order as:{quote}1. user specified before @ character in hostname string 2. login_name specified using -l switch 3. User option provided as a parameter to -o switch 4. User option in matching Host block from per-user config ~/.ssh/config 5. User option in matching Host block from systemwide config /etc/ssh/ssh_config If there is nothing from above specified, username on local terminal is used.{quote}The OpenSSH 7.7 login_name evaluation order is: # login_name specified using -l switch # user specified before @ character in hostname string # User option provided as a parametr to -o switch # User option in matching Host block from per-user config ~/.ssh/config # User option in matching Host block from systemwide config /etc/ssh/ssh_configIf there is nothing from above specified, username on local terminal is used.[OpenSSH Portable bug 2849|http://bugzilla.mindrot.org/show_bug.cgi?id=2849] has been submitted to track the change.Johannes Schindelin of the Git for Windows project has submitted a [pull request|https://github.com/openssh/openssh-portable/pull/91] to the OpenSSH Portable project. The OpenSSH project has closed the [bug report|http://bugzilla.mindrot.org/show_bug.cgi?id=2849] as "Won't Fix". Damien Miller states that the behavior change is intentional. I'll start the work to adjust the git client plugin and/or the git plugin to adapt to the OpenSSH behavior change.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Mark Waite edited a comment on JENKINS-50573
Re: Wrong username used for clone with Git 2.17 on Windows
OpenSSH 7.7 changed the order of evaluation of login_name. OpenSSH 7.7 is first bundled in Git for Windows 2.17.0. [OpenSSH bug 2385|http://bugzilla.mindrot.org/show_bug.cgi?id=2385] describes the prior order as:{quote}1. user specified before @ character in hostname string 2. login_name specified using -l switch 3. User option provided as a parameter to -o switch 4. User option in matching Host block from per-user config ~/.ssh/config 5. User option in matching Host block from systemwide config /etc/ssh/ssh_config If there is nothing from above specified, username on local terminal is used.{quote}The OpenSSH 7.7 login_name evaluation order is: # login_name specified using -l switch # user specified before @ character in hostname string # User option provided as a parametr to -o switch # User option in matching Host block from per-user config ~/.ssh/config # User option in matching Host block from systemwide config /etc/ssh/ssh_configIf there is nothing from above specified, username on local terminal is used.[OpenSSH Portable bug 2849|http://bugzilla.mindrot.org/show_bug.cgi?id=2849] has been submitted to track the change.Johannes Schindelin of the Git for Windows project has submitted a [pull request|https://github.com/openssh/openssh-portable/pull/91] to the OpenSSH Portable project. The OpenSSH project has closed the [bug report|http://bugzilla.mindrot.org/show_bug.cgi?id=2849 [ ] |http://bugzilla.mindrot.org/show_bug.cgi?id=2849] as "Won't Fix". Damien Miller states that the behavior change is intentional.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Mark Waite edited a comment on JENKINS-50573
Re: Wrong username used for clone with Git 2.17 on Windows
OpenSSH 7.7 changed the order of evaluation of login_name. OpenSSH 7.7 is first bundled in Git for Windows 2.17.0. [OpenSSH bug 2385|http://bugzilla.mindrot.org/show_bug.cgi?id=2385] describes the prior order as:{quote}1. user specified before @ character in hostname string 2. login_name specified using -l switch 3. User option provided as a parameter to -o switch 4. User option in matching Host block from per-user config ~/.ssh/config 5. User option in matching Host block from systemwide config /etc/ssh/ssh_config If there is nothing from above specified, username on local terminal is used.{quote}The OpenSSH 7.7 login_name evaluation order is: # login_name specified using -l switch # user specified before @ character in hostname string # User option provided as a parametr to -o switch # User option in matching Host block from per-user config ~/.ssh/config # User option in matching Host block from systemwide config /etc/ssh/ssh_configIf there is nothing from above specified, username on local terminal is used. [OpenSSH Portable bug 2849|http://bugzilla.mindrot.org/show_bug.cgi?id=2849] has been submitted to track the change. Johannes Schindelin of the Git for Windows project has submitted a [pull request|https://github.com/openssh/openssh-portable/pull/91] to the OpenSSH Portable project. It is not yet clear if The OpenSSH project has closed the [bug report|http://bugzilla.mindrot.org/show_bug.cgi?id=2849[]|http://bugzilla.mindrot.org/show_bug.cgi?id=2849] as "Won't Fix". Damien Miller states that the behavior change of order of evaluation is intentional or not .
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title Mark Waite commented on JENKINS-50573 Re: Wrong username used for clone with Git 2.17 on Windows OpenSSH 7.7 changed the order of evaluation of login_name. OpenSSH 7.7 is first bundled in Git for Windows 2.17.0. OpenSSH bug 2385 describes the prior order as: 1. user specified before @ character in hostname string 2. login_name specified using -l switch 3. User option provided as a parameter to -o switch 4. User option in matching Host block from per-user config ~/.ssh/config 5. User option in matching Host block from systemwide config /etc/ssh/ssh_config If there is nothing from above specified, username on local terminal is used. The OpenSSH 7.7 login_name evaluation order is: login_name specified using -l switch user specified before @ character in hostname string User option provided as a parametr to -o switch User option in matching Host block from per-user config ~/.ssh/config User option in matching Host block from systemwide config /etc/ssh/ssh_config If there is nothing from above specified, username on local terminal is used. OpenSSH Portable bug 2849 has been submitted to track the change. Johannes Schindelin of the Git for Windows project has submitted a pull request to the OpenSSH Portable project. It is not yet clear if that change of order of evaluation is intentional or not. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Mark Waite edited a comment on JENKINS-50573
Re: Wrong username used for clone with Git 2.17 on Windows
OpenSSH 7.7 changed the order of evaluation of login_name. OpenSSH 7.7 is first bundled in Git for Windows 2.17.0. [OpenSSH bug 2385|http://bugzilla.mindrot.org/show_bug.cgi?id=2385] describes the prior order as:{quote}1. user specified before @ character in hostname string 2. login_name specified using -l switch 3. User option provided as a parameter to -o switch 4. User option in matching Host block from per-user config ~/.ssh/config 5. User option in matching Host block from systemwide config /etc/ssh/ssh_config If there is nothing from above specified, username on local terminal is used.{quote}The OpenSSH 7.7 login_name evaluation order is: # login_name specified using -l switch # user specified before @ character in hostname string # User option provided as a parametr to -o switch # User option in matching Host block from per-user config ~/.ssh/config # User option in matching Host block from systemwide config /etc/ssh/ssh_configIf there is nothing from above specified, username on local terminal is used. [OpenSSH Portable bug 2849|http://bugzilla.mindrot.org/show_bug.cgi?id=2849] has been submitted to track the change. Johannes Schindelin of the Git for Windows project has submitted a [pull request|https://github.com/openssh/openssh-portable/pull/91] to the OpenSSH Portable project. It is not yet clear if that change of order of evaluation is intentional or not.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title Mark Waite edited a comment on JENKINS-50573 Re: Wrong username used for clone with Git 2.17 on Windows I've duplicated the problem in my environment. Alternatives include:# Enable JGit in your installation and configure the job to use JGit instead of command line git# Use Windows command line git 2.16.2 or earlierI'll start a conversation with the git for windows team to understand what may have changed in the handling of GIT_SSH authentication settings. The git plugin may need to be updated to follow the technique recommended in JENKINS-32883 if it detects a modern enough version of command line git. Problem appears to be specific to the Windows version of git 2.17.0. I compiled git 2.17.0 on Ubuntu 16.04 and used it successfully with the Jenkins git plugin. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title Mark Waite edited a comment on JENKINS-50573 Re: Wrong username used for clone with Git 2.17 on Windows I've duplicated the problem in my environment. Alternatives include:# Enable JGit in your installation and configure the job to use JGit instead of command line git# Use Windows command line git 2.16.2 or earlierI'll start a conversation with the git for windows team to understand what may have changed in the handling of GIT_SSH authentication settings. The git plugin may need to be updated to follow the technique recommended in JENKINS-32883 if it detects a modern enough version of command line git . Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title Mark Waite commented on JENKINS-50573 Re: Wrong username used for clone with Git 2.17 on Windows I've duplicated the problem in my environment. Alternatives include: Enable JGit in your installation and configure the job to use JGit instead of command line git Use Windows command line git 2.16.2 or earlier I'll start a conversation with the git for windows team to understand what may have changed in the handling of GIT_SSH authentication settings. The git plugin may need to be updated to follow the technique recommended in JENKINS-32883. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title Joe George updated an issue Jenkins / JENKINS-50573 Wrong username used for clone with Git 2.17 on Windows Change By: Joe George Environment: Windows Git 2.17 (specifically) from chocolatey Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Joe George updated an issue
Jenkins / JENKINS-50573
Wrong username used for clone with Git 2.17 on Windows
Change By:
Joe George
Our Windows VMs which updated to the latest Git on Windows (2.17) use the wrong username when cloning git repos. They're using {{jenkins}} when {{git}} it explicitly specified.{code:java}dir("dist-utils") {git credentialsId: 'ssh-id-rsa', url: 'ssh://g...@github.com/zeroc-ice/dist-utils.git'}{code}{code:java} > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url ssh://g...@github.com/zeroc-ice/dist-utils.git # timeout=10Fetching upstream changes from ssh://g...@github.com/zeroc-ice/dist-utils.git > git --version # timeout=10using GIT_SSH to set credentials Jenkins SSH RSA Key > git fetch --tags --progress ssh://g...@github.com/zeroc-ice/dist-utils.git +refs/heads/*:refs/remotes/origin/*ERROR: Error fetching remote repo 'origin'hudson.plugins.git.GitException: Failed to fetch from ssh://g...@github.com/zeroc-ice/dist-utils.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:862) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1129) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1160) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress ssh://g...@github.com/zeroc-ice/dist-utils.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: jenk...@github.com: Permission denied (publickey).fatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1996) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1715) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:405) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Joe George updated an issue
Jenkins / JENKINS-50573
Wrong username used for clone with Git 2.17 on Windows
Change By:
Joe George
Our Windows VMs which updated to the latest Git on Windows (2.17) use the wrong username when cloning git repos. They're using {{jenkins}} when {{git}} it explicitly specified.{code:java}dir("dist-utils") {git credentialsId: 'ssh-id-rsa', url: 'ssh://g...@github.com/zeroc-ice/dist-utils.git'}{code}{code:java} > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url ssh://g...@github.com/zeroc-ice/dist-utils.git # timeout=10Fetching upstream changes from ssh://g...@github.com/zeroc-ice/dist-utils.git > git --version # timeout=10using GIT_SSH to set credentials Jenkins SSH RSA Key > git fetch --tags --progress ssh://g...@github.com/zeroc-ice/dist-utils.git +refs/heads/*:refs/remotes/origin/*ERROR: Error fetching remote repo 'origin'hudson.plugins.git.GitException: Failed to fetch from ssh://g...@github.com/zeroc-ice/dist-utils.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:862) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1129) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1160) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress ssh://g...@github.com/zeroc-ice/dist-utils.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: jenk...@github.com: Permission denied (publickey).fatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1996) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1715) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:405) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Joe George updated an issue
Jenkins / JENKINS-50573
Wrong username used for clone with Git 2.17 on Windows
Change By:
Joe George
Our Windows VMs which updated to the latest Git on Windows (2.17) are somehow using use the wrong username when cloning git repos. They're using {{jenkins}} when {{git}} it explicitly specified. {code:java}dir("dist-utils") {git credentialsId: 'ssh-id-rsa', url: 'ssh://g...@github.com/zeroc-ice/dist-utils.git'}{code}{code:java} > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url ssh://g...@github.com/zeroc-ice/dist-utils.git # timeout=10Fetching upstream changes from ssh://g...@github.com/zeroc-ice/dist-utils.git > git --version # timeout=10using GIT_SSH to set credentials Jenkins SSH RSA Key > git fetch --tags --progress ssh://g...@github.com/zeroc-ice/dist-utils.git +refs/heads/*:refs/remotes/origin/*ERROR: Error fetching remote repo 'origin'hudson.plugins.git.GitException: Failed to fetch from ssh://g...@github.com/zeroc-ice/dist-utils.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:862) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1129) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1160) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress ssh://g...@github.com/zeroc-ice/dist-utils.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: jenk...@github.com: Permission denied (publickey).fatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1996) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1715) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:405) at
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Joe George created an issue
Jenkins / JENKINS-50573
Wrong username used for clone with Git 2.17 on Windows
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2018-04-04 16:01
Environment:
Windows Git 2.17 (specifically)
Priority:
Blocker
Reporter:
Joe George
Our Windows VMs which updated to the latest Git on Windows (2.17) are somehow using the wrong username when cloning git repos.
dir("dist-utils") {
git credentialsId: 'ssh-id-rsa', url: 'ssh://g...@github.com/zeroc-ice/dist-utils.git'
}
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url ssh://g...@github.com/zeroc-ice/dist-utils.git # timeout=10
Fetching upstream changes from ssh://g...@github.com/zeroc-ice/dist-utils.git
> git --version # timeout=10
using GIT_SSH to set credentials Jenkins SSH RSA Key
> git fetch --tags --progress ssh://g...@github.com/zeroc-ice/dist-utils.git +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from ssh://g...@github.com/zeroc-ice/dist-utils.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:862)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1129)
at
