jenkinsci / jenkinsci/github-branch-source-plugin

[JENKINS-65493] Multibranch reposiory filters should support exclusions and not just inclusions

Open
#1,354 0 comments 0 reactions 0 assignees View on GitHub
component:github-branch-source-plugin component:multibranch-build-strategy-extension-plu enhancement imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
217
Forks
398
Avg merge
30m
Merged PRs (30d)
1

Description

I'm using GitHub Branch Source as an example, but this may apply to all Multibranch Pipelines.

Currently, I have hundreds of repos in a GitHub organization.   Many have Jenkinsfiles.  I have one that I want Jenkins to ignore, even though it has Jenkinsfiles (it's already built in another GitHub/Jenkins hierarchy).  Options:



  1. Exclude Archived: I'd have to archive the repo, then I can't keep it up to date (it stores private tags)

  2. Exclude Public:  This can probably work in my case, but it's an odd heuristic to remember.

  3. Topics: an include-only filter.  I'd have to add the topic to all repos except one (and remember to do that for all new repos)

  4. Filter by Name: I couldn't find a regex/wildcard that would work as an exclusion.  Same issue as Topics.

  5. GitHub Team slug:  Maybe, but not any more obvious than "Exclude Public".

 

In short, I think that Topics and Filter by Name should have an Invert option.

---
Originally reported by akom, imported from: Multibranch reposiory filters should support exclusions and not just inclusions


  • assignee: igalg
  • status: Open
  • priority: Minor
  • component(s): github-branch-source-plugin, multibranch-build-strategy-extension-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 1
  • imported: 2025-12-02

Raw content of original issue

I'm using GitHub Branch Source as an example, but this may apply to all Multibranch Pipelines.

Currently, I have hundreds of repos in a GitHub organization.   Many have Jenkinsfiles.  I have one that I want Jenkins to ignore, even though it has Jenkinsfiles (it's already built in another GitHub/Jenkins hierarchy).  Options:



  1. Exclude Archived: I'd have to archive the repo, then I can't keep it up to date (it stores private tags)

  2. Exclude Public:  This can probably work in my case, but it's an odd heuristic to remember.

  3. Topics: an include-only filter.  I'd have to add the topic to all repos except one (and remember to do that for all new repos)

  4. Filter by Name: I couldn't find a regex/wildcard that would work as an exclusion.  Same issue as Topics.

  5. GitHub Team slug:  Maybe, but not any more obvious than "Exclude Public".

 

In short, I think that Topics and Filter by Name should have an Invert option.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.