[JENKINS-53959] Pipeline Git LFS avoid pull on Jenkins Master

When using declarative pipeline in a pipeline(not multibranch-pipeline) job and adding the additional behavior to "Git LFS pull after checkout".

This is actually done on master too. Which for very LARGE files seems over kill.

First off we don't have LFS installed on master.

Secondly we don't have that much storage allocated cause we never considered the master would be trying to pull from our LFS storage that is a job for our agents...

Unless I am mistaken I don't think this is the intended behavior.

Of course I could try an extension plugin that says avoids LFS checkout on master.

I would be happy to look into a solution for the git plugin if this is indeed not the intended behavior.

---
Originally reported by casz, imported from: Pipeline Git LFS avoid pull on Jenkins Master

• status: Open
  
• priority: Minor
  
• component(s): git-plugin
  
• resolution: Unresolved
  
• votes: 5
  
• watchers: 6
  
• imported: 2025-12-02
  

Raw content of original issue

When using declarative pipeline in a pipeline(not multibranch-pipeline) job and adding the additional behavior to "Git LFS pull after checkout".


This is actually done on master too. Which for very LARGE files seems over kill.


First off we don't have LFS installed on master.

 Secondly we don't have that much storage allocated cause we never considered the master would be trying to pull from our LFS storage that is a job for our agents... 


Unless I am mistaken I don't think this is the intended behavior.


Of course I could try an extension plugin that says avoids LFS checkout on master.


I would be happy to look into a solution for the git plugin if this is indeed not the intended behavior.