Pointer files are not replaced by the original files

[Natsuspace]

Pointer files are not replaced by the original files

[bk2204]

I'm sorry, I don't use Jenkins and don't know how it can be configured. Just as a note, I think, from some quick Googling, that there is a Jenkins task to check out LFS objects which invokes something like git lfs pull, which you might be able to use. git lfs pull, assuming it has the right credentials, should be sufficient to get the pointer files replaced by large files.

[bk2204]

Hey,

I don't think this is due to the smudge option; that appears normal. Can you provide a printout of the environment on that machine while Jenkins is running that task? The reason I ask is that if it contains GIT_LFS_SKIP_SMUDGE=1, then that will cause the pointer files to remain in the working tree and cause this problem.

[Natsuspace]

Hey,

I don't think this is due to the smudge option; that appears normal. Can you provide a printout of the environment on that machine while Jenkins is running that task? The reason I ask is that if it contains GIT_LFS_SKIP_SMUDGE=1, then that will cause the pointer files to remain in the working tree and cause this problem.

Yah, it does have this, How do I disable this?

            Name                                      Value   

17:40:09 GIT_LFS_SKIP_SMUDGE 1

[KalleOlaviNiemitalo]

The Git plugin for Jenkins defines the "Git LFS pull after checkout" behaviour that you can add to a branch source in a pipeline project. I don't remember whether it covers submodules too.

Alternatively, you can use the sh or bat or pwsh pipeline step to run the git lfs pull command, perhaps combined with git submodule foreach. However, Jenkins does not automatically pass the Git repository access credentials to such commands. So if your repository is private, then you may have to place the command within a withCredentials step and configure the credential in Jenkins so that the pipeline is authorised to use it.

[Natsuspace]

Hey,

I don't think this is due to the smudge option; that appears normal. Can you provide a printout of the environment on that machine while Jenkins is running that task? The reason I ask is that if it contains GIT_LFS_SKIP_SMUDGE=1, then that will cause the pointer files to remain in the working tree and cause this problem.

I tried after setting the GIT_LFS_SKIP_SMUDGE to 0, but the issue still exists