Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-52857

Cannot find git-lfs when it is not installed in /usr/bin/

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • git-plugin
    • None
    • OSX

      We have an issue on our OSX nodes, where we cannot checkout a repo with git-lfs.

      We suppose that it is related to that `checkout scm` listens `/usr/bin/` and it is not possible to install anything there because of Apple's system integrity. Even passing a PATH=$PATH:/usr/local/bin doesn't take any effect. 

      Tested this with a ssh nods and `git checkout` works (as we have user credentials and all the simlinks), but as all of our nodes use JNLP we would like to have a possibility to define path to git-lfs like we can do for git.

      Stack trace:

      hudson.plugins.git.GitException: Command "/usr/local/bin/git checkout -f 304f1c283e1fa22e47ea9d7be1e2582a93021819" returned status code 128:
       stdout: 
       stderr: git-lfs filter-process: git-lfs: command not found
       fatal: The remote end hung up unexpectedly
      at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2002)
       at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$800(CliGitAPIImpl.java:72)
       at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2301)
       Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 172.31.128.169/172.31.128.169:49241
       at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)
       at hudson.remoting.UserResponse.retrieve(UserRequest.java:389)
       at hudson.remoting.Channel.call(Channel.java:955)
       at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)
       at sun.reflect.GeneratedMethodAccessor638.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
       at java.lang.reflect.Method.invoke(Method.java:498)
       at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)
       at com.sun.proxy.$Proxy117.execute(Unknown Source)
       at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1236)
       at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113)
       at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85)
       at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75)
       at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
       at hudson.security.ACL.impersonate(ACL.java:290)
       at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
       at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
       at java.util.concurrent.FutureTask.run(FutureTask.java:266)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
       at java.lang.Thread.run(Thread.java:748)
       Caused: hudson.plugins.git.GitException: Could not checkout 304f1c283e1fa22e47ea9d7be1e2582a93021819
       at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2325)
       at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
       at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
       at hudson.remoting.UserRequest.perform(UserRequest.java:210)
       at hudson.remoting.UserRequest.perform(UserRequest.java:53)
       at hudson.remoting.Request$2.run(Request.java:358)
       at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
       at java.util.concurrent.FutureTask.run(FutureTask.java:264)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
       at hudson.remoting.Engine$1$1.run(Engine.java:94)
       at java.lang.Thread.run(Thread.java:844)
       Finished: FAILURE
      

       

          [JENKINS-52857] Cannot find git-lfs when it is not installed in /usr/bin/

          Mark Waite added a comment -

          Since I don't have access to a Mac, I can't test the case you're describing. Can you confirm that you installed git LFS on the mac following the git-lfs instructions?

          Mark Waite added a comment - Since I don't have access to a Mac, I can't test the case you're describing. Can you confirm that you installed git LFS on the mac following the git-lfs instructions ?

          Serghei Moret added a comment -

          sure, git-lfs is installed. I can do: 

          sh 'git checkout master'

          but not

          checkout scm

          Serghei Moret added a comment - sure, git-lfs is installed. I can do:  sh 'git checkout master' but not checkout scm

          Serghei Moret added a comment - - edited

          Also, I don't think that mac is needed to reproduce. What is needed is git-lfs installed in /usr/local/bin and JNLP connection to the node. 

           

          Mac problem is only that you cannot install anything to /usr/bin even with rooted user.

          Serghei Moret added a comment - - edited Also, I don't think that mac is needed to reproduce. What is needed is git-lfs installed in /usr/local/bin and JNLP connection to the node.    Mac problem is only that you cannot install anything to /usr/bin even with rooted user.

          Serghei Moret added a comment -

          What we miss is possibility to define location of git-lfs binary, so `checkout scm` command could work

          Serghei Moret added a comment - What we miss is possibility to define location of git-lfs binary, so `checkout scm` command could work

          Mark Waite added a comment - - edited

          I wasn't able to duplicate the problem you're reporting, even on a JNLP based agent with git-lfs (and git) in the /usr/local/bin directory. Steps I took:

          1. Confirm that git and git-lfs are installed in /usr/local/bin in the 'git' jail of my FreeNAS server
          2. Configure a JNLP agent to run from a Jenkins 2.121.2 master based on the docker-lfs image
          3. Declare the location of the Default git tool on that agent as /usr/local/bin/git
          4. Run Freestyle and Pipeline jobs on that agent which confirm it is able to use LFS repositories

          See the attached picture for the configuration details

          Mark Waite added a comment - - edited I wasn't able to duplicate the problem you're reporting, even on a JNLP based agent with git-lfs (and git) in the /usr/local/bin directory. Steps I took: Confirm that git and git-lfs are installed in /usr/local/bin in the 'git' jail of my FreeNAS server Configure a JNLP agent to run from a Jenkins 2.121.2 master based on the docker-lfs image Declare the location of the Default git tool on that agent as /usr/local/bin/git Run Freestyle and Pipeline jobs on that agent which confirm it is able to use LFS repositories See the attached picture for the configuration details

          Serghei Moret added a comment -

          markewaite thanks a lot for looking into it! I have the same settings but it fails, so maybe it is really related to OSX

          Serghei Moret added a comment - markewaite thanks a lot for looking into it! I have the same settings but it fails, so maybe it is really related to OSX

          I am having the same issue on OSX, with my git and git lfs installed through brew. This has happened on two iMacs for me (one fresh install, one existing/in use)

          Thomas Roberts added a comment - I am having the same issue on OSX, with my git and git lfs installed through brew. This has happened on two iMacs for me (one fresh install, one existing/in use)

          I have the same issue as Serghei, OSX, and git-lfs is installed at --system.  Similarly, I cannot move the git-lfs binary to /usr/bin because of Apple System Integrity.   Hoping for some help on this one, we do a lot of xCode builds that we want to move to an OSX Slave.  

           

          Anything I can provide to help here?

          Andrew LoPinto added a comment - I have the same issue as Serghei, OSX, and git-lfs is installed at --system.  Similarly, I cannot move the git-lfs binary to /usr/bin because of Apple System Integrity.   Hoping for some help on this one, we do a lot of xCode builds that we want to move to an OSX Slave.     Anything I can provide to help here?

          Mark Waite added a comment -

          alopinto I think the best way you could help would be to debug on a macOS machine to see why command line git launched from the Jenkins git client plugin can't find the git LFS binary.

          I don't have a macOS machine. It works on FreeBSD as I expected. FreeBSD is the closest approximation I have to macOS.

          For example, you might investigate (with Java debugger or otherwise):

          • PATH setting of command line git when run on macOS
          • Homebrew special cases (if any) for git on macOS
          • Workarounds like installing command line git outside homebrew (in case that allows git-lfs to be found)

          Mark Waite added a comment - alopinto I think the best way you could help would be to debug on a macOS machine to see why command line git launched from the Jenkins git client plugin can't find the git LFS binary. I don't have a macOS machine. It works on FreeBSD as I expected. FreeBSD is the closest approximation I have to macOS. For example, you might investigate (with Java debugger or otherwise): PATH setting of command line git when run on macOS Homebrew special cases (if any) for git on macOS Workarounds like installing command line git outside homebrew (in case that allows git-lfs to be found)

          I believe it's to do with the PATH. The way I got it to work was by disabling the Apple System Integrity and symbolic linking the git-lfs from /usr/local/bin to /usr/bin. When the plugin uses git, it seems to use a PATH that only has /usr/bin in it and not /usr/local/bin, because I even set the PATH to have /usr/local/bin first before using the command 'checkout scm' but it still doesn't find git-lfs. Also git-lfs works if I manually call 'git checkout ...' so it's something specific to the git scm plugin for jenkins.

          Thomas Roberts added a comment - I believe it's to do with the PATH. The way I got it to work was by disabling the Apple System Integrity and symbolic linking the git-lfs from /usr/local/bin to /usr/bin. When the plugin uses git, it seems to use a PATH that only has /usr/bin in it and not /usr/local/bin, because I even set the PATH to have /usr/local/bin first before using the command 'checkout scm' but it still doesn't find git-lfs. Also git-lfs works if I manually call 'git checkout ...' so it's something specific to the git scm plugin for jenkins.

          Mark Waite added a comment - - edited

          Does it work with Apple System Integrity enabled if the environment of the macOS agent adds the environment variable:

          PATH+GIT_LFS=/usr/local/bin
          

          I use that technique on my agents to set the PATH environment variable for some jobs that aren't equipped to use the Jenkins global tool configuration.

          In my configuration, it looks like this:

          Mark Waite added a comment - - edited Does it work with Apple System Integrity enabled if the environment of the macOS agent adds the environment variable: PATH+GIT_LFS=/usr/local/bin I use that technique on my agents to set the PATH environment variable for some jobs that aren't equipped to use the Jenkins global tool configuration. In my configuration, it looks like this:

          Hi,

          I have exactly same issue with Linux node.

          My Linux image is predefined without git. I use git and git lfs from custom location. git work, but git lfs doesn`t.

          I`ve tried all recommendations about reconfigured PATH from this discussion. It doesn`t work. Git plugin still looks git lfs at /usr/bin. 

          Ilya Evseenkov added a comment - Hi, I have exactly same issue with Linux node. My Linux image is predefined without git. I use git and git lfs from custom location. git work, but git lfs doesn`t. I`ve tried all recommendations about reconfigured PATH from this discussion. It doesn`t work. Git plugin still looks git lfs at /usr/bin. 

          Mark Waite added a comment - - edited

          btk3000 can you provide a step by step description that will allow someone else to duplicate the problem you're seeing?

          I can't duplicate this problem in my attempts with FreeBSD. I don't have access to macOS.

          All my Linux installations include git and they all find git lfs whether the git lfs package is provided by the operating system (Debian Testing), provided by a separate operating system package (Debian 8), or separately installed (CentOS 7).

          Mark Waite added a comment - - edited btk3000 can you provide a step by step description that will allow someone else to duplicate the problem you're seeing? I can't duplicate this problem in my attempts with FreeBSD. I don't have access to macOS. All my Linux installations include git and they all find git lfs whether the git lfs package is provided by the operating system (Debian Testing), provided by a separate operating system package (Debian 8), or separately installed (CentOS 7).

          Hi Mark,

          I`m using core 2.107.3 and git plugin 3.9.1.

          My Linux node runs CentOS 6.7. 

          When I do "git --version" on it, I get "git version 1.7.1".

           

          I installed another git into "/anotherfs/git-2.19.0/" and added it "Manage Jenkins->Global Tools configuration->git". I didn`t re-configured PATH, "which git" still point "/usr/bin/git"

           

          After that, I added git lfs like "/anotherfs/git-2.19.0/bin/git lfs install". 

          Command "/anotherfs/git-2.19.0/bin/git-lfs version" shows "git-lfs/2.4.0 (GitHub; linux amd64; go 1.8.3; git 1a98fa5c)"

           

          After that I`m configuring my Pipeline job with Jenkinsfile and "Git LFS pull after checkout". It works on master and get Jenkinsfile, but at node:
          hudson.plugins.git.GitException: Command "/anotherfs/git-2.19.0/bin/git checkout -f f52336bc40265a1f8703eac49b89cd6b7a778df7" returned status code 128:
          stdout:
          stderr: git-lfs filter-process: git-lfs: command not found
           

          It happens, because "/anotherfs/git-2.19.0/bin/" is not in the PATH.

          If I add/overwrite PATH at node configuration page, git plugin ignores it and use OS version of PATH.

           

          If I add "PATH" from console, it works too,

           

          Hope. it is enough )

           

          Ilya Evseenkov added a comment - Hi Mark, I`m using core 2.107.3 and git plugin 3.9.1. My Linux node runs CentOS 6.7.  When I do "git --version" on it, I get "git version 1.7.1".   I installed another git into "/anotherfs/git-2.19.0/" and added it "Manage Jenkins->Global Tools configuration->git". I didn`t re-configured PATH, "which git" still point "/usr/bin/git"   After that, I added git lfs like "/anotherfs/git-2.19.0/bin/git lfs install".  Command "/anotherfs/git-2.19.0/bin/git-lfs version" shows "git-lfs/2.4.0 (GitHub; linux amd64; go 1.8.3; git 1a98fa5c)"   After that I`m configuring my Pipeline job with Jenkinsfile and "Git LFS pull after checkout". It works on master and get Jenkinsfile, but at node: hudson.plugins.git.GitException: Command "/anotherfs/git-2.19.0/bin/git checkout -f f52336bc40265a1f8703eac49b89cd6b7a778df7" returned status code 128: stdout: stderr: git-lfs filter-process: git-lfs: command not found   It happens, because "/anotherfs/git-2.19.0/bin/" is not in the PATH. If I add/overwrite PATH at node configuration page, git plugin ignores it and use OS version of PATH.   If I add "PATH" from console, it works too,   Hope. it is enough )  

          Mark Waite added a comment -

          btk3000 thanks for the step-by-step description. It sounds like the problem is incorrect use of the defined git tool in all the cases where it might be used. Since there is a workaround, I'm unlikely to investigate this further.

          Mark Waite added a comment - btk3000 thanks for the step-by-step description. It sounds like the problem is incorrect use of the defined git tool in all the cases where it might be used. Since there is a workaround, I'm unlikely to investigate this further.

          Iurii Mark added a comment -

          After downgrading plugin "Analysis Model API" from 2.1.2 to 2.1.1 I was able to checkout sources on Mac.

          Note that the issue is reproducible only with "Analysis Model API" 2.1.2 and Nodes that have "Launch method" set to "Launch agent agents via SSH"

          Iurii Mark added a comment - After downgrading plugin "Analysis Model API" from 2.1.2 to 2.1.1 I was able to checkout sources on Mac. Note that the issue is reproducible only with "Analysis Model API" 2.1.2 and Nodes that have "Launch method" set to "Launch agent agents via SSH"

          Mark Waite added a comment -

          vurda I would be truly amazed if the Analysis Model API plugin downgrade were the root cause of the problem, especially since this problem was reported before Analysis Model API 2.0 was released.

          I don't know why the behavior changed when you downgraded. It could be that the downgrade also included a Jenkins restart. It could be that the restart from the downgrade changed some startup ordering or caused the PATH to be initialized differently.

          Mark Waite added a comment - vurda I would be truly amazed if the Analysis Model API plugin downgrade were the root cause of the problem, especially since this problem was reported before Analysis Model API 2.0 was released. I don't know why the behavior changed when you downgraded. It could be that the downgrade also included a Jenkins restart. It could be that the restart from the downgrade changed some startup ordering or caused the PATH to be initialized differently.

          Filip Trönnbergq added a comment - - edited

          We had the exact same problem but were able to get this to work by going to "Manage Jenkins -> Configure System" and adding an environment variable called "PATH+EXTRA" with the value /usr/local/bin.

          After initially attempting to manually set the path we saw the following output in the console that suggested the use of "PATH+EXTRA"

          Warning: JENKINS-41339 probably bogus PATH=""$PATH":/usr/local/bin":/usr/local/bin; perhaps you meant to use 'PATH+EXTRA=/something/bin'?

          Filip Trönnbergq added a comment - - edited We had the exact same problem but were able to get this to work by going to "Manage Jenkins -> Configure System" and adding an environment variable called "PATH+EXTRA" with the value /usr/local/bin. After initially attempting to manually set the path we saw the following output in the console that suggested the use of "PATH+EXTRA" Warning: JENKINS-41339 probably bogus PATH=""$PATH":/usr/local/bin":/usr/local/bin; perhaps you meant to use 'PATH+EXTRA=/something/bin'?

          Lars Bilke added a comment -

          I have the exact same issue but none of the workarounds helped.

          Lars Bilke added a comment - I have the exact same issue but none of the workarounds helped.

          Jeff Meador added a comment -

          I have a different workaround.

          Run this command to see where your git programs are stored.

          git --exec-path 

          If you want to be sure it's the correct git binary, use the full path.

          /usr/bin/git --exec-path  

          or

          /usr/local/bin/git --exec-path 

          For me that command outputs the following directory. This is where you want to put git-lfs.

           /usr/local/git/libexec/git-core

          You could copy git-lfs into there or create a link so git-lfs can be updated in the original location.

          sudo ln -s /usr/local/bin/git-lfs /usr/local/git/libexec/git-core/git-lfs

          That's it, it was able to find git-lfs after that.

          Jeff Meador added a comment - I have a different workaround. Run this command to see where your git programs are stored. git --exec-path If you want to be sure it's the correct git binary, use the full path. /usr/bin/git --exec-path or /usr/local/bin/git --exec-path For me that command outputs the following directory. This is where you want to put git-lfs. /usr/local/git/libexec/git-core You could copy git-lfs into there or create a link so git-lfs can be updated in the original location. sudo ln -s /usr/local/bin/git-lfs /usr/local/git/libexec/git-core/git-lfs That's it, it was able to find git-lfs after that.

          Lars Bilke added a comment - - edited

          Thanks Jeff, this works for me too! I had set up this symlink (I use Homebrew):

          ln -s /usr/local/bin/git-lfs /usr/local/Cellar/git/2.21.0/libexec/git-core/git-lf

          And for Macports:

          sudo ln -s `which git-lfs` /opt/local/libexec/git-core/git-lfs
          

          Lars Bilke added a comment - - edited Thanks Jeff, this works for me too! I had set up this symlink (I use Homebrew): ln -s /usr/local/bin/git-lfs /usr/local/Cellar/git/2.21.0/libexec/git-core/git-lf And for Macports: sudo ln -s `which git-lfs` /opt/local/libexec/git-core/git-lfs

          Devin Lane added a comment - - edited

          I just worked through this issue today and have found a reasonable solution. First, the problem lies in the way that Jenkins makes a connection to the slave; apparently, the "checkout" command uses an environment obtained from a non-interactive login, and BEFORE environment from Jenkins node config takes place. The rest of the build uses a "normal" environment so you may find that git lfs commands work there.

          One method of fixing this is to alter /etc/ssh/sshd_config (for macOS), set "PermitUserEnvironment" to YES, then restart sshd. Next, edit /Users/Jenkins/.ssh/environment and set PATH="$PATH:/usr/local/bin" etc as required. Finally, have Jenkins reconnect to the slave to pick up the new environment.

          More details at https://support.cloudbees.com/hc/en-us/articles/229724088-How-to-set-up-a-Jenkins-agent-to-have-the-same-path-as-the-user-when-connected-via-Remote-Desktop-

          Devin Lane added a comment - - edited I just worked through this issue today and have found a reasonable solution. First, the problem lies in the way that Jenkins makes a connection to the slave; apparently, the "checkout" command uses an environment obtained from a  non-interactive login, and BEFORE environment from Jenkins node config takes place. The rest of the build uses a "normal" environment so you may find that git lfs commands work there. One method of fixing this is to alter /etc/ssh/sshd_config (for macOS), set "PermitUserEnvironment" to YES, then restart sshd. Next, edit /Users/Jenkins/.ssh/environment and set PATH="$PATH:/usr/local/bin" etc as required. Finally, have Jenkins reconnect to the slave to pick up the new environment. More details at  https://support.cloudbees.com/hc/en-us/articles/229724088-How-to-set-up-a-Jenkins-agent-to-have-the-same-path-as-the-user-when-connected-via-Remote-Desktop-

          Rory Dungan added a comment -

          Had the same problem on Mac. Setting environment variables in the node properties didn't seem to help since it looks like they are applied to "Execute shell" job stages but not the checkout stage.

          Another workaround I found is to create a shell script that sets the PATH variable and then runs Git:

          #!/bin/sh
          export PATH=/usr/local/bin:$PATH
          git "$@"
          

          Then in the Jenkins node properties screen, set the Git executable to that script:

          Feels like a bit of a hack but hopefully someone else finds it useful

          Rory Dungan added a comment - Had the same problem on Mac. Setting environment variables in the node properties didn't seem to help since it looks like they are applied to "Execute shell" job stages but not the checkout stage. Another workaround I found is to create a shell script that sets the PATH variable and then runs Git: #!/bin/sh export PATH=/usr/local/bin:$PATH git "$@" Then in the Jenkins node properties screen, set the Git executable to that script: Feels like a bit of a hack but hopefully someone else finds it useful

          Mark Waite added a comment - - edited

          The same condition exists for OpenBSD environment variables.

          The sshd_config on OpenBSD (and macOS) does not allow Jenkins to set environment variables unless the PermitUserEnvironment is set to YES as recommended by devinlane

          I encountered the problem because I could not find my PATH adjustments to locate Maven and Ant in the non-default locations where I store them.

          Mark Waite added a comment - - edited The same condition exists for OpenBSD environment variables. The sshd_config on OpenBSD (and macOS) does not allow Jenkins to set environment variables unless the PermitUserEnvironment is set to YES as recommended by devinlane I encountered the problem because I could not find my PATH adjustments to locate Maven and Ant in the non-default locations where I store them.

          Xin Meng added a comment -

          still have the issue. i try lots of methods, even copying the git lfs to the same path with git, but still fail to execute. no idea how to resolve it now. 

          I think this problem is very important for mac user.

          Xin Meng added a comment - still have the issue. i try lots of methods, even copying the git lfs to the same path with git, but still fail to execute. no idea how to resolve it now.  I think this problem is very important for mac user.

          Mark Waite added a comment -

          mengxin did you try the workaround proposed by Devin Lane?  It worked for me on my OpenBSD machine.

          Mark Waite added a comment - mengxin did you try the workaround proposed by Devin Lane?  It worked for me on my OpenBSD machine.

          Xin Meng added a comment -

          markewaite  Thanks for your reply, but in my case, I do not have a slave instance. all Jenkins running on my single mac computer. 

          I tried this before: https://smashswift.com/jenkins-does-not-recognize-git-lfs-on-mac/

          it works on my previous computer, but on the new one does not work. 

           

          Xin Meng added a comment - markewaite   Thanks for your reply, but in my case, I do not have a slave instance. all Jenkins running on my single mac computer.  I tried this before: https://smashswift.com/jenkins-does-not-recognize-git-lfs-on-mac/ it works on my previous computer, but on the new one does not work.   

          Xin Meng added a comment -

          currently i am testing another workwround:

           

          cp /usr/local/bin/git-lfs /usr/local/Cellar/git/2.36.1/libexec/git-core/

           

          seem like work, but waiting for final checkout result

          Xin Meng added a comment - currently i am testing another workwround:   cp /usr/local/bin/git-lfs /usr/local/Cellar/git/2.36.1/libexec/git-core/   seem like work, but waiting for final checkout result

          Xin Meng added a comment -

          finally

           

          https://smashswift.com/jenkins-does-not-recognize-git-lfs-on-mac/

          cp /usr/local/bin/git-lfs /usr/local/Cellar/git/2.36.1/libexec/git-core/

           

          works

          Xin Meng added a comment - finally   https://smashswift.com/jenkins-does-not-recognize-git-lfs-on-mac/ +  cp /usr/local/bin/git-lfs /usr/local/Cellar/git/2.36.1/libexec/git-core/   works

          S added a comment -

          sudo ln -s `which git-lfs` `git --exec-path`/git-lfs

          S added a comment - sudo ln -s `which git-lfs` `git --exec-path`/git-lfs

            Unassigned Unassigned
            joesss Serghei Moret
            Votes:
            5 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated: