Organization Folders

Organization Folders Across a GitHub Account

An Organization Folder goes one level up: it scans every repository of a GitHub 29 organization, or of a user account, and creates a Multibranch Pipeline for each one that contains a Jenkinsfile. New repositories are picked up without anyone creating a job. The folder binarybehemoth points at the author's personal account, with the same credential and a Filter by name (with regular expression) trait of booknest-jenkins.*, so that it never builds anything outside this chapter:

The organization scan, filtered to the lines about BookNestGroovy
J=http://localhost:32080
curl -s -u "admin:$JENKINS_TOKEN" $J/job/binarybehemoth/computation/consoleText \
  | grep -E 'Looking up repositories|booknest-jenkins|branches were|repositories were|^Finished'
Output
Looking up repositories of myself binarybehemoth
Proposing booknest-jenkins
Examining binarybehemoth/booknest-jenkins
  1 branches were processed
Finished examining binarybehemoth/booknest-jenkins
1 repositories were processed
Finished: SUCCESS

"Of myself" means the plugin recognized the token's own user account, not an organization. Every other repository was logged as "Ignoring ..." and not examined. The folder created binarybehemoth/booknest-jenkins, duplicating booknest, and was deleted afterward: in practice you choose one style. Organization webhooks and teams need a real organization: not run here.