[JENKINS-52212] Job Inclusion Strategy: Regex

I would like to propose a new and possibly easy to implement Strategy for Job Inclusion: per Regex (from the job name).

It should not be based on what's in a view or folder, but solely on the name of the job.

 

Additional benefit: one could then also set "part\ of\ whatever.*" as regex to catch currently unsupported pipeline heavyweight jobs (created by node() command) - might be a bit crude, but it would help a lot.

---
Originally reported by beyerj, imported from: Job Inclusion Strategy: Regex

• status: Open
  
• priority: Major
  
• component(s): prioritysorter-plugin
  
• resolution: Unresolved
  
• votes: 2
  
• watchers: 4
  
• imported: 20251211-071809
  

Raw content of original issue

I would like to propose a new and possibly easy to implement Strategy for Job Inclusion: per Regex (from the job name).


It should not be based on what's in a view or folder, but solely on the name of the job.


 


Additional benefit: one could then also set "part\ of\ whatever.*" as regex to catch currently unsupported pipeline heavyweight jobs (created by node() command) - might be a bit crude, but it would help a lot.

Start by locating the existing job inclusion strategies in this Jenkins plugin and their tests; no specific files or entry points are named in the issue. Define the regex strategy around matching job names rather than views or folders, including the provided pipeline-job example. Done means the strategy can be configured and its matching behavior is covered by tests.

Written by the indexing model from the issue text.