[JENKINS-61826] gerrit-trigger add support for sparse checkout in dynamic trigger.

I see a need to have support for sparse checkout in the dynamic trigger.

There is support for file patterns for the triggering but that can not be used for spare checkout.

 

We have some repositories that are huge, and I'm only interesting of part of the project.

I guess the gerrit-trigger need to set an environment variable for the paths that can be accessed from the Jenkins pipeline.

 

---
Originally reported by martin5403, imported from: gerrit-trigger add support for sparse checkout in dynamic trigger.

• assignee: rsandell
  
• status: Open
  
• priority: Minor
  
• component(s): gerrit-trigger-plugin
  
• resolution: Unresolved
  
• votes: 1
  
• watchers: 1
  
• imported: 2025-12-07
  

Raw content of original issue

I see a need to have support for sparse checkout in the dynamic trigger.


There is support for file patterns for the triggering but that can not be used for spare checkout.


 


We have some repositories that are huge, and I'm only interesting of part of the project.


I guess the gerrit-trigger need to set an environment variable for the paths that can be accessed from the Jenkins pipeline.


 

Start by reviewing the dynamic trigger and its existing file-pattern handling; the issue names no files or tests. Define how sparse-checkout paths should be supplied and exposed to the Jenkins pipeline, then add support and verify that only the requested repository paths are available.

Written by the indexing model from the issue text.