[JENKINS-33588] Branches and Repositories prioritization

As a development team with github organization account and with limited CI servers bandwidth we would like to have commits on production branches to be built before the intermediate commits to personal development branches.

In addition some repositories are more critical then the others, so builds for that repositories need to be prioritized.

In Jenkins 1.x I could manage this with Priority Sorter Plugin in combination with Views and Jobs properties.

I could not find a way to do it for the organization folder with pipeline as code.

For example for Git Flow I need branches that match 'hotfix/.' have more priority than 'master' branch which is above 'release/.' branches which is above Dev branch and above all the other branches.

One more job type in Jenkins 2.0 is Pull Request. There might be Pull request to hot fix branches/to master/to release/to feature development branches, while there is no way to determine this. It makes sense to prioritize it by PR title.

---
Originally reported by vorobievalex, imported from: Branches and Repositories prioritization

• status: Open
  
• priority: Major
  
• component(s): prioritysorter-plugin
  
• label(s): github, pipeline
  
• resolution: Unresolved
  
• votes: 3
  
• watchers: 7
  
• imported: 20251211-071809
  

As a development team with github organization account and with limited CI servers bandwidth we would like to have commits on production branches to be built before the intermediate commits to personal development branches.

In addition some repositories are more critical then the others, so builds for that repositories need to be prioritized.


In Jenkins 1.x I could manage this with Priority Sorter Plugin in combination with Views and Jobs properties.

I could not find a way to do it for the organization folder with pipeline as code.


For example for Git Flow I need branches that match 'hotfix/.' have more priority than 'master' branch which is above 'release/.' branches which is above Dev branch and above all the other branches.

One more job type in Jenkins 2.0 is Pull Request. There might be Pull request to hot fix branches/to master/to release/to feature development branches, while there is no way to determine this. It makes sense to prioritize it by PR title.

• environment: Jenkins 2.0, organization folders