[JENKINS-26868] Add "repack after cloning" option to the 'reference' support in git clone

I like using the --reference support in the additional clone options to provide a pre-cache for a remote git server, but would prefer that the cloned repositories not have the persistent 'alternates' referenced - even though the remotes are read only.

Would like to see a checkbox in the 'Additional Clone Behaviors' config section for the reference to say "Repack after Clone" to run 'git repack -a'. This would obviously negate space savings, but still accomplishes the goal of avoiding network transfer when the primary repository is on a remote slow link.

---
Originally reported by nneul, imported from: Add "repack after cloning" option to the 'reference' support in git clone

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

I like using the --reference support in the additional clone options to provide a pre-cache for a remote git server, but would prefer that the cloned repositories not have the persistent 'alternates' referenced - even though the remotes are read only. 


Would like to see a checkbox in the 'Additional Clone Behaviors' config section for the reference to say "Repack after Clone" to run 'git repack -a'. This would obviously negate space savings, but still accomplishes the goal of avoiding network transfer when the primary repository is on a remote slow link.