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

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

Mark Waite updated an issue

Jenkins / JENKINS-55948 Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked Change By: Mark Waite Summary: Git client 3.0.0 pre - rc release called from git parameter plugin fails, 2.x worked Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

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

Mark Waite commented on JENKINS-55948

Re: Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked I've seen the problem in git client 3.0.0 pre-releases and occasionally in git client plugin 2.8.x I've corrected the description to show that the issue is most visible with git client plugin 3.0.0 pre-release versions, including the most recent pre-release.

Add Comment

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

Mark Waite commented on JENKINS-55948

Re: Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked

Carlos Garcia I'm not aware of anything in the changes between git client plugin 2.8.0 and 2.8.2 which would cause any difference in this behavior. However, since I don't know the root of the problem, I can't be certain that 2.8.2 will work in your environment.

Add Comment

[cgarcia@intesis.com (JIRA)]

Carlos Garcia commented on JENKINS-55948

Re: Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked

Git Client plugin has been officially released with version 3.0.0, but this issue seems to be still open. Is the problem solved? Is it safe to use the recently released v3.0.0?

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

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

Mark Waite commented on JENKINS-55948

Re: Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked

The problem is not solved by any change in git client plugin 3.0.0. I've seen the problem in git client plugin 2.8.x and in git client plugin 3.0.0 pre-releases (as mentioned in the earlier comment).

Add Comment

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

Mark Waite edited a comment on JENKINS-55948

Re: Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked

The problem is not solved by any change in git client plugin 3.0.0.  I've seen the problem in git client plugin 2.8.x and in git client plugin 3.0.0 pre-releases (as mentioned in the my [earlier comment|https://issues.jenkins-ci.org/browse/JENKINS-55948?focusedCommentId=374806&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-374806] and in the [earlier comment|https://issues.jenkins-ci.org/browse/JENKINS-55948?focusedCommentId=373982&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-373982] from Jose B ).

Add Comment

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

Mark Waite edited a comment on JENKINS-55948

Re: Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked

The problem is not solved by any change in git client plugin 3.0.0.  I've seen the problem in git client plugin 2.8.x and in git client plugin 3.0.0 pre-releases (as mentioned in my [earlier comment|https://issues.jenkins-ci.org/browse/JENKINS-55948?focusedCommentId=374806&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-374806] and in the [earlier comment|https://issues.jenkins-ci.org/browse/JENKINS-55948?focusedCommentId=373982&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-373982] from Jose B). However, the freestyle job in my test environment no longer shows the problem.  I can freely switch between parameter values without any failures.

Add Comment

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

Mark Waite edited a comment on JENKINS-55948

Re: Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked

The problem is not solved by any change in git client plugin 3.0.0.  I've seen the problem in git client plugin 2.8.x and in git client plugin 3.0.0 pre-releases (as mentioned in my [earlier comment|https://issues.jenkins-ci.org/browse/JENKINS-55948?focusedCommentId=374806&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-374806] and in the [earlier comment|https://issues.jenkins-ci.org/browse/JENKINS-55948?focusedCommentId=373982&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-373982] from Jose B).

However, the freestyle job in my test environment (git client plugin 3.0.0) no longer shows the problem.  I can freely switch between parameter values without any failures.   I don't know if it will resolve it for you, but I cannot see the problem in my current environment

Add Comment

[malcolm.hannah@pressureprofile.com (JIRA)]

Malcolm Hannah commented on JENKINS-55948

Re: Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked

Another data point: git client 2.9.0 has been working fine for me for several weeks.  (On Jenkins 2.190.1, git plugin 3.12.1)

Add Comment

[cgarcia@intesis.com (JIRA)]

Carlos Garcia commented on JENKINS-55948

Re: Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked

I updated git client to 3.0.0 so that we can test if any problem arises with that. We will see if the problem with v3.0.0 was finally solved (intentionally or not ). This could take weeks to reproduce, so let's wait.

Add Comment

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

Mark Waite resolved as Fixed

Carlos Garcia since there was no reply here, I assume that the issue is resolved with git client plugin 3.0.0 and later. You're welcome to reopen the issue with more details if it is not resolved.

Jenkins / JENKINS-55948

Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked

Change By: Mark Waite Status: Open Resolved Resolution: Fixed

Add Comment

[marcus.a.philip@gmail.com (JIRA)]

Marcus Philip commented on JENKINS-55948

Re: Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked I had the same symptoms, ie cat: command not found error: unable to read askpass response from ... fatal: could not read Username for 'http://<omitted by me>': No such device or address Eventually I realized that I had a build param called 'path'. Go figure the rest for yourself... When I renamed it, everything worked fine. This is probably another bug that should be reported somewhere, it's absolutely crazy that you can affect the PATH of the git commands this way, but maybe they'll say working as designed

Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)