[JIRA] (JENKINS-55948) Git client plug-in crash
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.
[JIRA] (JENKINS-55948) Git client plug-in crash
Title: Message Title Mark Waite commented on JENKINS-55948 Re: Git client plug-in crash Malcolm Hannah thanks for the further insights. I've reopened the report but will need more information about the conditions where you see the problem. Can you attach the config.xml of the job that is showing the problem? What job type are you using? I assume Freestyle Can you confirm that the git repository URL is either http or https and that it is not one of the ssh types? Is the master running as a war on the operating system or are you running from inside a docker container? Are there any messages in the system log related to PATH? 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.
[JIRA] (JENKINS-55948) Git client plug-in crash
Title: Message Title Mark Waite updated JENKINS-55948 Jenkins / JENKINS-55948 Git client plug-in crash Change By: Mark Waite Status: In Review Progress 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.
[JIRA] (JENKINS-55948) Git client plug-in crash
Title: Message Title Mark Waite updated JENKINS-55948 Jenkins / JENKINS-55948 Git client plug-in crash Change By: Mark Waite Resolution: Cannot Reproduce Status: Resolved In Review 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.
[JIRA] (JENKINS-55948) Git client plug-in crash
Title: Message Title Mark Waite stopped work on JENKINS-55948 Change By: Mark Waite Status: In Progress Open 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.
[JIRA] (JENKINS-55948) Git client plug-in crash
Title: Message Title
Malcolm Hannah commented on JENKINS-55948
Re: Git client plug-in crash
I can duplicate this issue. Please let me know how I could help to resolve it. In case it's helpful, here are my own observations:
The problem only happens with private repositories (I'm working with GitHub).
The problem seems to only happen when populating the branch selector (command 'git ls-remote'). If I proceed with the default branch, the job completes successfully, and the build log shows commands such as git fetch, git rev-parse and git checkout succeeding, after GIT_ASKPASS.
A different error occurs ("remote: Invalid username or password.") if I configure the project to use 'none' credentials instead of real credentials. I suppose in this case there is no need to generate and run a shell script.
I first noticed this problem after updating Jenkins and all plugins at the end of January.
I'm running Jenkins 2.150.3 on Ubuntu 16.04.6 LTS. Plugin versions: git parameter 0.9.10, git client 3.0.0-rc. In fstab, the tmpfs flags are rw,nosuid,nodev. The cat command is in /bin.
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.
[JIRA] (JENKINS-55948) Git client plug-in crash
Title: Message Title Mark Waite updated JENKINS-55948 Jenkins / JENKINS-55948 Git client plug-in crash Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Cannot Reproduce 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.
[JIRA] (JENKINS-55948) Git client plug-in crash
Title: Message Title Mark Waite updated JENKINS-55948 Jenkins / JENKINS-55948 Git client plug-in crash Change By: Mark Waite Status: Fixed but Unreleased Resolved 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.
[JIRA] (JENKINS-55948) Git client plug-in crash
Title: Message Title Mark Waite commented on JENKINS-55948 Re: Git client plug-in crash The message: cat: command not found error: unable to read askpass response from '/tmp/jenkins-gitclient-pass2775860834031002260.sh' indicates that the shell which is trying to executed the cat command from inside a shell script cannot find the cat command on the PATH. The cat command is installed in /bin/cat on Red Hat and CentOS machines. If the shell cannot find it, then something has been seriously damaged. Possible damaged things might include: Temporary file system mounted with noexec flag Temporary file system exhausted available inodes or available space Shell environment damaged by shell startup script changes Memory exhausted Swap space exhausted Since Carlos Garcia can't duplicate it and others can't duplicate it, I'm closing this as "cannot duplicate" 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.
[JIRA] (JENKINS-55948) Git client plug-in crash
Title: Message Title
Karl Shultz edited a comment on JENKINS-55948
Re: Git client plug-in crash
[~carlosgarcia] - what version of the {{git}} and {{git-client}} plugins are you running right now? You can see this by looking at https://your-jenkins:jenkins-port/pluginManager/installed. Should look something like this: !image-2019-02-05-12-46-05-024.png|thumbnail!I ask because there is currently a release-candidate version of both of these plugins, on the experimental update center.
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.
[JIRA] (JENKINS-55948) Git client plug-in crash
Title: Message Title
Karl Shultz edited a comment on JENKINS-55948
Re: Git client plug-in crash
[~carlosgarcia] - what version of the {{git}} and {{git-client}} plugins are you running right now? You can see this by looking at https://your-jenkins:jenkins-port/pluginManager/installed. Should look something like this: !image-2019-02-05-12-46-05-024.png|thumbnail! I ask because there is currently a release-candidate version of both of these plugins, on the experimental update center. I'd like to know if you're running this early-release version, or the current version. Thanks!
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.
[JIRA] (JENKINS-55948) Git client plug-in crash
Title: Message Title Karl Shultz commented on JENKINS-55948 Re: Git client plug-in crash Carlos Garcia - what version of the git and git-client plugins are you running right now? You can see this by looking at https://your-jenkins:jenkins-port/pluginManager/installed. Should look something like this: I ask because there is currently a release-candidate version of both of these plugins, on the experimental update center. 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.
[JIRA] (JENKINS-55948) Git client plug-in crash
Title: Message Title Carlos Garcia commented on JENKINS-55948 Re: Git client plug-in crash After rebooting the Jenkins server (yes, the physical machine), these jobs seems to work normally again. Maybe the updates messed up with something (paths or whatever). For now, let's see how much time it takes to have problems again... 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.
[JIRA] (JENKINS-55948) Git client plug-in crash
Title: Message Title Carlos Garcia commented on JENKINS-55948 Re: Git client plug-in crash In order to reproduce the issue (at least before rebooting the server, which is a Centos) you only needed to configure a Free-style job with the following: Git parameter, showing up all the tags/branches for a specific Git repo Git clone for the same repo Nothing else After successive attempts, you may find that the branches never shows in git-parameter list, you will be given the "angry Jenkins" image and the stack trace instead. For now, I'm not able to reproduce it again. 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.
[JIRA] (JENKINS-55948) Git client plug-in crash
Title: Message Title Carlos Garcia commented on JENKINS-55948 Re: Git client plug-in crash I managed to reproduce the issue without the use of 'multiple-scm' plugin. So, the culprit must be git-client or git-parameter. With this simpler environment it took about 10~15 builds to make it fail. Once it fails, it fails forever and the job needs to be re-created. Another interesting thing is that if I simply copy the job, the problem is fixed (until it fails again). 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.
[JIRA] (JENKINS-55948) Git client plug-in crash
Title: Message Title Carlos Garcia commented on JENKINS-55948 Re: Git client plug-in crash I wanted to add that the problem started at an undetermined day after 24-Jan-2019. 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.
[JIRA] (JENKINS-55948) Git client plug-in crash
Title: Message Title Carlos Garcia created an issue Jenkins / JENKINS-55948 Git client plug-in crash Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin, git-parameter-plugin, multiple-scms-plugin Created: 2019-02-04 11:36 Environment: Latest Jenkins 2.150.2 All plugins updated Priority: Major Reporter: Carlos Garcia I have several jobs in which I can choose branches from a "multiple-scm" (i.e. several Git repos that are needed to compile a project). The first time the job is configured, it shows all the branches (one git-parameter for each Git repo), and it build ok. The problem arises when a job has been already built. For the non-first attempt, I always end up with the following crash: Stack trace hudson.plugins.git.GitException: Command "git ls-remote -h http://.git" returned status code 128: stdout: stderr: /tmp/jenkins-gitclient-pass2775860834031002260.sh: line 3: cat: command not found error: unable to read askpass response from '/tmp/jenkins-gitclient-pass2775860834031002260.sh' fatal: could not read Username for 'http://': No such device or address at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2318) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1905) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1805) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1796) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteReferences(CliGitAPIImpl.java:3170) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.getBranch(GitParameterDefinition.java:392) at
