Build Agent doesn`t support git-lfs

If I read it correctly you use the locally installed git version? In that case shouldn't you manually install git-lfs on that system? 

>If I read it correctly you use the locally installed git version? In that case shouldn't you manually install git-lfs on that system? 
I have showed data from the build machine where git installed.

That wasn't clear for me from the random command lines. Did you setup TeamCity to use the locally installed git instead of it's internal one? And can you manually execute the commands on the system to checkout the repository?

>Did you setup TeamCity to use the locally installed git instead of it's internal one?
git have been installed as well on machine

>And can you manually execute the commands on the system to checkout the repository?
I can build the project manually via command line if you meant this

if you have 

Native Git operations:	enabled

under Diagnostics > Git

And you have rebooted the system after Git installation.

Then I'm unsure what the possible problem could be.

I have deleted git-lfs that I have installed manual.
In the  Diagnostics > Git

resolved- need to delete local  git-lfs support from your build machine.

UPD:
>resolved- need to delete local  git-lfs support from your build machine.
after this the error still exists.

result of git lfs install is Git LFS initialized.

Failed to perform checkout on agent:  command failed.
  exit code: 128
  stderr: git-lfs filter-process: git-lfs: command not found
  fatal: the remote end hung up unexpectedly

export PATH=/usr/local/bin:$PATH
export PATH=/usr/local/bin/git-lfs:$PATH

Pavel Bahratsou

Pavel Bahratsou

Hello Pavel,

Did you manage to resolve the problem?

I am having the same issue with TeamCity Professional 2023.05 (build 129203). 

Failed to perform checkout on agent: /usr/bin/git -c credential.helper= checkout -q -f master command failed. exit code: 128 stderr: git-lfs filter-process: git-lfs: command not found fatal: the remote end hung up unexpectedly

git-lfs program is available to all systems, even I click for "Open Terminal" on a build agent, however in every checkout there is a problem with "git-lfs" not being found.

Niels, maybe you have some more ideas on this one?

Thanks!

Anatoly Cherenkov

Thanks for the comment, although it was unhelpful.

TL;DR I managed solve the problem by creating a symbolic link to git lfs executable: https://stackoverflow.com/a/69007609

At version 2024.3 TeamCity supports the https protocol for submodule and lfs. I wonder how to deal with http lfs? Since many in-house dedicated lfs repos (with different ip with repo) are employed just with http protocol instead of https.

Kethers Hi,

You're correct, accessing submodule repositories and LFS files is currently supported only via secure HTTPS protocol. Using HTTP for such access seems unsafe to me. However, if you think there is a valid scenario where it can be used safely, I suggest creating a feature request in our issue tracker and describing your scenario in detail there: https://youtrack.jetbrains.com/issues/TW.

Best regards,
Anton

Hi Anton Vakhtel ,

    Which version did you test http work? Is http dedicated lfs server supported in 2024.12? Since I have tried 2024.7 before and it's not working. When checkout another branch at build, it will forever stuck at credentials helper to access the dedicated lfs server until it reaches timeout limit. 

    If 2024.12 works fine then I will try update to newer version. By the way how to set the param for dedicated lfs/submodule? Do http/https share the same parameter names or not?

    It would be great if you can share more precise information with me, or please inform me when documentation adjustment is done.

Best Regards.

The conclusion, for everyone finding this discussion later:

We have confirmed that HTTP URL in teamcity.git.https.credentials.<ALIAS>.url works (TeamCity 2024.12).