You might be able to write an SCM trait extension plugin to understand repository topics filtering, however, I think you would need to send a Pull Request to the Github Branch Source plugin to have the topics data available from the API wrapper :)
GitHub API wrapper used by GitHub Branch Source plugin https://github.com/kohsuke/github-api/blob/master/src/main/java/org/kohsuke/github/GHRepository.java https://developer.github.com/v3/repos/#list-organization-repositories the topics is definitely on the repo :) Den torsdag den 8. marts 2018 kl. 07.28.37 UTC+1 skrev Cuong Tran: > > Joseph, > > Thanks for pointing me to that instance. Without admin access, I can only > guess that these grouping are manually defined. I'm looking for a more > dynamic way to group them (for example, using github topic) without relying > on the naming pattern alone. > > On Wednesday, March 7, 2018 at 8:34:09 PM UTC-8, Joseph P wrote: >> >> Take a look at https://ci.jenkins.io >> <https://www.google.com/url?q=https%3A%2F%2Fci.jenkins.io&sa=D&sntz=1&usg=AFQjCNG6KNAp1Lg_VxwmmerdGctEObs8Xg> >> >> they categorize repos into meaningful groups for instance Plugins folder >> contains all repos with the name *-plugin in the repo name. >> >> Den torsdag den 8. marts 2018 kl. 05.24.57 UTC+1 skrev Cuong Tran: >>> >>> How do folks manage a large number of repositories in a single >>> organization when you use the Github Branch Source to automatically create >>> jobs? >>> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9b71d4fa-6494-4c23-a292-a2ece46b8a93%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
