Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-71599

strategies for sub-dividing a github-org into different folders

      we have historically used github-enterprise (ghe) which is more liberal about creating distinct organizations, recently our company is looking to use github.com which does not lend itself to creating many organizations. so where we once had hundreds of ghe organizations, we would now have one large github.com organization and rely on github teams to represent "sub-organizations" within the company.

      currently, i am only aware of a regular/wild-card expression type match to filter repos for inclusion into a github-org.

      my new feature suggestion for this plugin would be to allow for one or more alternate strategies to identify repos from an org for inclusion in a github-org construct, for instance, one obvious strategy comes to mind which is the association of a repo with a team.

      another option could be regular/wild-card expression match for a string found in a particular file name (e.g. `github-org.dat`).

      these would be alternate strategies for filtering repos for an org when filtering off repo name is not practical for some reason.

       

       

          [JENKINS-71599] strategies for sub-dividing a github-org into different folders

          Mark Waite added a comment -

          The GitHub branch source plugin provides "Filter by repository topic" that I use to choose a subset of repositories based on the topic assigned to the repository. It also has exclude private repositories, exclude public repositories, exclude repositories that are forks of other repositories, and filters by the GitHub team "slug". Those all seem like very useful ways to subset a large organization.

          Mark Waite added a comment - The GitHub branch source plugin provides "Filter by repository topic" that I use to choose a subset of repositories based on the topic assigned to the repository. It also has exclude private repositories, exclude public repositories, exclude repositories that are forks of other repositories, and filters by the GitHub team "slug". Those all seem like very useful ways to subset a large organization.

            Unassigned Unassigned
            tony_k tony kerz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: