[JIRA] (JENKINS-55948) Git client plug-in crash

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title

Mark Waite commented on JENKINS-55948   Re: Git client plug-in crash Malcolm Hannah I believe I've found a way to duplicate the same conditions, though I don't understand the root of the problem yet, and won't do more investigation for a while. The steps I took to duplicate the problem using the Jenkins image from my docker_lfs repository are: Create a Freestyle job 'JENKINS-55948-cat-not-found-with-git-parameter-plugin' Parameterized with git parameter plugin using the parameter 'USER_BRANCH' of type 'Branch' with default value 'master' Use a private git https repository - https://github.com/MarkEWaite/bin Set branches to build as '${USER_BRANCH}' Run the job (in my case I ran it once successfully, then changed the repository URL and ran it a second time) When I try to run the job, it begins to present the list of branches as candidates to choose in the parameter, then reports the following error text: The default value has been returned An error occurred while download data Command "git ls-remote -h https://github.com/MarkEWaite/bin" returned status code 128: stdout: stderr: /tmp/jenkins-gitclient-pass3357881948490999049.sh: 3: /tmp/jenkins-gitclient-pass3357881948490999049.sh: cat: not found error: unable to read askpass response from '/tmp/jenkins-gitclient-pass3357881948490999049.sh' fatal: could not read Username for 'https://github.com': terminal prompts disabled Please look at the Log Please check the configuration I think that indicates there is likely a bug in git client plugin 3.0.0-rc when it is called from the git parameter plugin. The git parameter plugin has not changed how it is calling the git client plugin, so I'm reasonably confident the issue is in git client plugin 3.0.0-rc. The near term solution for you is to downgrade from git client plugin 3.0.0-rc to the most recent officially released git client plugin, 2.7.4. You'll also need to downgrade the git plugin from 4.0.0-rc to 3.9.3. My apologies if your use of git client plugin 3.0.0 release candidate was unintentional. I made a mistake when I chose the version number string. I had intended for the 3.0.0-rc version of the plugin to only be visible in the experimental update center. Unfortunately, the version string I chose, '3.0.0-rc' is not hidden from the standard update center like '3.0.0-alpha' and '3.0.0-beta' are. The cat command that is used in the authentication is an intentional change in git client plugin 3.0.0 which will allow shell special characters in passwords. The previous versions of the git client plugin did not allow shell special characters in passwords. Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.