[JIRA] (JENKINS-55948) Git client 3.0.0-rc called from git parameter plugin fails, 2.x worked

13 views
Skip to first unread message

mark.earl.waite@gmail.com (JIRA)

unread,
Mar 1, 2019, 9:42:02 AM3/1/19
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
 
Jenkins / Bug JENKINS-55948
Git client 3.0.0-rc called from git parameter plugin fails, 2.x worked
Change By: Mark Waite
Summary: Git client 3.0.0-rc use by called from git parameter plugin is incompatible with git client fails, 2.x worked
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

malcolm.hannah@pressureprofile.com (JIRA)

unread,
Mar 1, 2019, 10:51:02 AM3/1/19
to jenkinsc...@googlegroups.com
Malcolm Hannah commented on Bug JENKINS-55948
 
Re: Git client 3.0.0-rc called from git parameter plugin fails, 2.x worked

Mark Waite thank you very much for looking into this and for finding a work-around so quickly.  (I should've come here sooner - I've been struggling with this on and off for weeks!)

 

Downgrading git-client to 2.7.5 and git plugin to 3.9.3 appears to have fixed it for me.

 

I say 'appears to' as my investigations earlier today (before the downgrades) led to some projects being 'fixed' as I stripped them down to a bare minimum example, then experimented with selecting the wrong credentials, then selecting the right credentials etc.  However, I didn't manage to isolate any single particular action that fixed them.

 

For the record, the answers to your earlier questions are:

Freestyle project, https repo, master is war on non-virtual non-containerised Ubuntu, nothing relevant in the system log.

 

mark.earl.waite@gmail.com (JIRA)

unread,
Mar 12, 2019, 8:32:02 AM3/12/19
to jenkinsc...@googlegroups.com
Mark Waite assigned an issue to Unassigned
 
Change By: Mark Waite
Assignee: Mark Waite

cgarcia@intesis.com (JIRA)

unread,
May 15, 2019, 9:30:04 AM5/15/19
to jenkinsc...@googlegroups.com
Carlos Garcia commented on Bug JENKINS-55948
 
Re: Git client 3.0.0-rc called from git parameter plugin fails, 2.x worked

This problem happened again, and it is not resolved by simply restarting Jenkins server.

I tried the downgrade and it seems to work for now, fortunately. The problem appears only in jobs with Git Parameters (where I can choose a branch/tag). In this case, an error is thrown and no branches are shown.

 

Is there any progress on this? It is a strange issue, since my 'cat' command is available:

  1. whereis cat
    cat: /usr/bin/cat /usr/share/man/man1/cat.1.gz

 

  1. cat --version
    cat (GNU coreutils) 8.22
    Copyright (C) 2013 Free Software Foundation, Inc.
    License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
    This is free software: you are free to change and redistribute it.
    There is NO WARRANTY, to the extent permitted by law.

Written by Torbjörn Granlund and Richard M. Stallman.

 

Thanks in advance!

mark.earl.waite@gmail.com (JIRA)

unread,
May 15, 2019, 9:35:03 AM5/15/19
to jenkinsc...@googlegroups.com

Carlos Garcia The best "work around" is to not use git client plugin 3.0.0-rc and to not use git plugin 4.0.0-rc. No solution is available yet for those pre-release versions. I've flagged this bug as a blocking bug that must be fixed before the release of git client plugin 3.0.0 and git plugin 4.0.0.

josebarragan@craftercode.com (JIRA)

unread,
Aug 25, 2019, 7:49:02 AM8/25/19
to jenkinsc...@googlegroups.com

Same problem here. 

org.jenkins-ci.plugins:git:3.12.0

git version 2.16.5

{{}}

hudson.plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/develop:refs/remotes/origin/develop --prune" returned status code 128:
 stdout: 
 stderr: fatal: cannot exec '/var/jenkins_home/caches/git-65d92e97f92a73450ba94ed072b567ff@tmp/pass3737312687055551151.sh': Permission denied
 fatal: could not read Username for 'https://gitlab.internal.into' : terminal prompts disabled

 

Any solution ahead!?

josebarragan@craftercode.com (JIRA)

unread,
Aug 25, 2019, 7:50:02 AM8/25/19
to jenkinsc...@googlegroups.com
Jose Barragan edited a comment on Bug JENKINS-55948
Same problem here. 

org.jenkins-ci.plugins:git:3.12.0

git version 2.16.5

{
{}}
{ code:java}

hudson.plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/develop:refs/remotes/origin/develop --prune" returned status code 128:
stdout:
stderr: fatal: cannot exec '/var/jenkins_home/caches/git-65d92e97f92a73450ba94ed072b567ff@tmp/pass3737312687055551151.sh': Permission denied
fatal: could not read Username for 'https://gitlab.internal.into' : terminal prompts disabled{code}
 

Any solution ahead!?

josebarragan@craftercode.com (JIRA)

unread,
Aug 25, 2019, 7:53:03 AM8/25/19
to jenkinsc...@googlegroups.com
Jose Barragan edited a comment on Bug JENKINS-55948
Same problem here. 

org.jenkins-ci.plugins:git:3.12.0
org.jenkins-ci.plugins:git-client:2.8.2
git version 2.16.5

{code:java}
hudson.plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/develop:refs/remotes/origin/develop --prune" returned status code 128:
stdout:
stderr: fatal: cannot exec '/var/jenkins_home/caches/git-65d92e97f92a73450ba94ed072b567ff@tmp/pass3737312687055551151.sh': Permission denied
fatal: could not read Username for 'https://gitlab.internal.into' : terminal prompts disabled{code}
 

Any solution ahead!?

josebarragan@craftercode.com (JIRA)

unread,
Aug 25, 2019, 9:17:02 AM8/25/19
to jenkinsc...@googlegroups.com

I downgrade Git Plugin a Git-Client Plugin and get the same problem

org.jenkins-ci.plugins:git:3.9.3
org.jenkins-ci.plugins:git-client:2.7.6
git version 2.16.5
Jenkins Version 2.190

cgarcia@intesis.com (JIRA)

unread,
Sep 4, 2019, 8:47:03 AM9/4/19
to jenkinsc...@googlegroups.com

There is a new update for git-client (2.8.2).

Is it safe to use? Given Jose Barragan comment, it seems not . I would like to know before updating if it will cause any issue (I have 2.8.0 and it is working fine).

bmathus+ossjira@cloudbees.com (JIRA)

unread,
Sep 4, 2019, 5:30:02 PM9/4/19
to jenkinsc...@googlegroups.com

Please create a new Jira issue if you encounter problems. This one is specificly about the 3.0.0-rc that is now hidden from the Update Center.

BTW Mark Waite should we close this now to be clearer that this very one is resolved? Thanks!
Reply all
Reply to author
Forward
0 new messages