Hello Mark, When I use Git Client Plugin 1.13.0, I'm not getting -c core.askpass=true.
But when I use, 1.14.0, its using that option but you have released the change in 1.14.1. Could you please let me know how I can skip this particular step in Git Client Plugin 1.14.0 1.14.1 (Dec 27, 2014) - Only use "-c core.askpass=true" if command line git is newer than 1.7.9 (don't break really old git versions unnecessarily) 1.14.0 (Dec 25, 2014) - Update from JGit 3.5.3 to JGit 3.6.0 - Use command line credentials check when using command line git (issue #22675 <http://issues.jenkins-ci.org/browse/JENKINS-22675>, issue #22909 <http://issues.jenkins-ci.org/browse/JENKINS-22909>, issue #23050 <http://issues.jenkins-ci.org/browse/JENKINS-23050>, issue #20533 <http://issues.jenkins-ci.org/browse/JENKINS-20533>) On Wednesday, January 28, 2015 at 10:01:24 AM UTC+5:30, Mark Waite wrote: > > The "-c core.askpass=true" is used to prevent the git command line call > from prompting for a password from stdin. It was added in a recent > git-client-plugin and was a key change to enable resolution of several > other bugs. I doubt very much that argument is causing an authentication > problem. > > On Tue, Jan 27, 2015 at 9:15 AM, Rob Mandeville <[email protected] > <javascript:>> wrote: > >> I am using: >> >> · Jenkins 1.580.2 >> >> · GIT client plugin 1.15.0 >> >> · GIT plugin 2.3.4 >> >> · Workflow plugins 1.1 >> >> · Credentials plugin 1.22 >> >> >> >> We use GitLab for source control and do not allow anonymous access of any >> kind. We use the Credentials plugin, have put in credentials allowing us >> access to Git, and on our normal projects, we simply give Git these >> pre-loaded credentials. Now, I’m trying to create a Workflow job. >> >> >> >> I can’t find any doc which says how to feed credentials to Git, so I went >> to the credentials plugin and pulled the plugin ID from the URL. I then >> wrote the following Groovy CPS DSL script (without the redactions, >> obviously): >> >> >> >> >> >> steps.stage('Setup') >> >> node('mock_builder') { >> >> String templateUrl = 'git@URL_REDACTED' >> >> steps.git(url: templateUrl, credentialsId: 'ID_REDACTED') >> >> sh 'echo hello world' >> >> } >> >> >> >> The job gets stuck in the SCM step and exits with the following output: >> >> >> >> Running: Setup >> >> Entering stage Setup >> >> Proceeding >> >> Running: Allocate node : Start >> >> Running on mock_builder in >> C:\Windows\TEMP\hudson1572436821107746068tmp\workspace\Try a Workflow >> >> Running: Allocate node : Body : Start >> >> Running: Git >> >> > git.exe rev-parse --is-inside-work-tree # timeout=10 >> >> Fetching changes from the remote Git repository >> >> > git.exe config remote.origin.url git@URL_REDACTED # timeout=10 >> >> Fetching upstream changes from git@URL_REDACTED >> >> > git.exe --version # timeout=10 >> >> > git.exe -c core.askpass=true fetch --tags --progress git@URL_REDACTED >> +refs/heads/*:refs/remotes/origin/* >> >> ERROR: Timeout after 10 minutes >> >> ERROR <http://stacktrace.jenkins-ci.org/search?query=ERROR>: Error fetching >> remote repo 'origin' >> >> Running <http://stacktrace.jenkins-ci.org/search?query=Running>: Allocate >> node : Body : End >> >> Running: Allocate node : End >> >> Running: End of Workflow >> >> ERROR: Error fetching remote repo 'origin' >> >> Finished <http://stacktrace.jenkins-ci.org/search?query=Finished>: FAILURE >> >> >> >> I’m wondering where the “-c core.askpass=true” came from, and figuring >> that it was waiting to receive a password via standard input. >> >> Is there any way, with or without the credentials plugin, to feed Git >> credentials to this project? >> > > The "-c core.askpass=true" is used to prevent the git command line call > from prompting for a password from stdin. It was added in a recent > git-client-plugin and was a key change to enable resolution of several > other bugs. I doubt very much that argument is causing an authentication > problem. > > >> Thanks in advance, >> >> >> >> --Rob >> >> ------------------------------ >> This e-mail and the information, including any attachments it contains, >> are intended to be a confidential communication only to the person or >> entity to whom it is addressed and may contain information that is >> privileged. If the reader of this message is not the intended recipient, >> you are hereby notified that any dissemination, distribution or copying of >> this communication is strictly prohibited. If you have received this >> communication in error, please immediately notify the sender and destroy >> the original message. >> >> Thank you. >> >> Please consider the environment before printing this email. >> >> -- >> 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/0A40042D85E7C84DB443060EC44B3FD36D9ACEDA91%40dekaexchange07.deka.local >> >> <https://groups.google.com/d/msgid/jenkinsci-users/0A40042D85E7C84DB443060EC44B3FD36D9ACEDA91%40dekaexchange07.deka.local?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > 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/29112111-e2f5-4d62-b916-011e72dbfae2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
