[JIRA] (JENKINS-59433) git clone fails on osx client with lfs
Title: Message Title Will Wagner updated JENKINS-59433 Jenkins / JENKINS-59433 git clone fails on osx client with lfs Change By: Will Wagner Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202017.1568816731000.1772.1575581640293%40Atlassian.JIRA.
[JIRA] (JENKINS-59433) git clone fails on osx client with lfs
Title: Message Title Will Wagner commented on JENKINS-59433 Re: git clone fails on osx client with lfs I was not able to reproduce this with a simple multi-branch pipeline job. However now I revisit this I am not able to reproduce the problem at all using gerrit as the source. I think this can be closed as an error on some part by me. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202017.1568816731000.11888.1575452280118%40Atlassian.JIRA.
[JIRA] (JENKINS-59433) git clone fails on osx client with lfs
Title: Message Title Luca Domenico Milanesio commented on JENKINS-59433 Re: git clone fails on osx client with lfs Can you reproduce the problem with a simple Git multi-branch pipeline job? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202017.1568816731000.5959.1574630040126%40Atlassian.JIRA.
[JIRA] (JENKINS-59433) git clone fails on osx client with lfs
Title: Message Title Will Wagner created an issue Jenkins / JENKINS-59433 git clone fails on osx client with lfs Issue Type: Bug Assignee: lucamilanesio Components: gerrit-code-review-plugin Created: 2019-09-18 14:25 Environment: Jenkins 2.176.3 gerrit-code-review-plugin 0.4-SNAPSHOT-ca8c2fde Priority: Minor Reporter: Will Wagner This may be more a question than a bug, wasn't able to find a mailing list though for this kind of thing. I have setup a multibranch pipeline using the gerrit source. This is working fine on a windows client machine but is failing on an osx client machine. The console output of the failure is: "using credential 6e96f729-8440-40bf-8710-88689c791d3b Cloning the remote Git repository Cloning with configured refspecs honoured and without tags Cloning repository https://##/magpie > /usr/local/bin/git init /var/lib/jenkins/workspace/magpie-verify_13_5713_6 # timeout=10 Fetching upstream changes from https://##/magpie > /usr/local/bin/git --version # timeout=10 using GIT_ASKPASS to set credentials > /usr/local/bin/git fetch --no-tags --force --progress https://##/magpie +refs/heads/:refs/remotes/origin/ +refs/changes/:refs/remotes/origin/ # timeout=10 Fetching without tags Checking out Revision 0d966917fd54323445d54cce6c33e3283b5dc435 (13/5713/6) Enabling Git LFS pull" I believe the error is because it cannot find the git-lfs executable but I'm not entirely certain. If I create a basic jenkins job and use git to clone the repository then this works fine. This works because in the node configuration I have added /usr/local/bin to the path. (I believe osx doesn't put /usr/local/bin in the path for a non-interactive ssh environment) My guess as to what is happening is that the custom path set on the node is not being passed to the
