[JENKINS-45435] Allow overriding configuration in a per-project basis

The GitHub Branch Source plugin is great to manage big organizations by having a folder that auto-scans projects, but also big organization have a lot of different kinds of projects. Because of this is hard that one configuration will fit all the projects, for example, include/exclude branches to build.

Currently one can look at one project's config, but it's read-only. It would be nice to be able to override these configurations on a per-project basis. Even better, it would be good to be able to control these overrides directly via Jenkinsfile (although I know is tricky as you might not even want to look at the Jenkinsfile if it's excluded).

---
Originally reported by lucasocio, imported from: Allow overriding configuration in a per-project basis

• status: Open
  
• priority: Minor
  
• component(s): github-branch-source-plugin
  
• label(s): org-folder
  
• resolution: Unresolved
  
• votes: 3
  
• watchers: 3
  
• imported: 2025-12-02
  

The GitHub Branch Source plugin is great to manage big organizations by having a folder that auto-scans projects, but also big organization have a lot of different kinds of projects. Because of this is hard that one configuration will fit all the projects, for example, include/exclude branches to build.


Currently one can look at one project's config, but it's read-only. It would be nice to be able to override these configurations on a per-project basis. Even better, it would be good to be able to control these overrides directly via Jenkinsfile (although I know is tricky as you might not even want to look at the Jenkinsfile if it's excluded).