Thank you for your suggestions. I am new to Jenkins, but I did look at the Pipeline approach with a Jenkinsfile. It occurred to me that an "innocent" student might choose to change the content of the file. That might not be a good thing. I am also concerned that the Github Organization plugin appears to be at end-of-life.
I have just discovered the Generic Webhook Trigger, and have successfully implemented it on my Jenkins instance and with a webhook at the organization level in Github. Seems to work. I have successfully passed four bits of information from the JSON data in the webhook payload to my build script, and now I just need to put in some front-end code to identify which assignment is being submitted. That information can come from the prefix of the repo name. I will continue to look at using Pipelines (mainly because that is all the Jenkins docs want to talk about) but i will go with my Generic Trigger solution until I my requirements force me in a different direction. ...ted On Fri, Jul 20, 2018 at 6:25 AM, Jan Monterrubio <[email protected]> wrote: > This definitely sounds like what Mark suggested. If you set up the GitHub > service and webhook, Jenkins can build on every push to any branch in a > repository. > > You’ll need to make sure the repositories have a jenkinsfile: > https://jenkins.io/doc/book/pipeline/jenkinsfile/ > > You’ll probably need some plugins like the GitHub branch source and maybe > GitHub organization. > > On Thu, Jul 19, 2018 at 22:43 Mark Waite <[email protected]> > wrote: > >> I think you want a "GitHub Organization" project. It will scan an entire >> organization then create and destroy jobs based on the presence of a >> Jenkinsfile in the root directory of one or more branches in the >> repositories that it finds. >> >> Mark Waite. >> >> On Thu, Jul 19, 2018 at 9:26 PM Ted Cowan <[email protected]> wrote: >> >>> I am a college instructor that is automating the submission of >>> programming assignments using GitHub Classroom. Typically we have 50 >>> students, each submitting 9 assignments per semester. All of the repos are >>> part of one organization, and I wish to trigger a build and test when each >>> student pushes to their private repo. >>> >>> Is this possible in Jenkins, and if so, how? There are myriad examples >>> of how to trigger a build on a single repo, but I need to trigger the same >>> build when any of 50 repos are changed. I hope this doesn't mean I have to >>> add the names of all 50 repos to each job, but that might be doable if I >>> edit the config.xml outside of Jenkins. >>> >>> ...ted >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" 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-users/56757380-01d9-45ef-9123- >>> b0b732ab819b%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/56757380-01d9-45ef-9123-b0b732ab819b%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" 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-users/CAO49JtGVtSZVSZ_Hddyte7aZhZ_ >> Cu%2BwB%2BF2Vu49euXEPDSvLTA%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGVtSZVSZ_Hddyte7aZhZ_Cu%2BwB%2BF2Vu49euXEPDSvLTA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/jenkinsci-users/4xUNCOLdpfI/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-users/CADgiF9Kd0cvtmMQyUXs4a9FOtetev > TBSU50vt%3DiNDaJLmsVCbQ%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CADgiF9Kd0cvtmMQyUXs4a9FOtetevTBSU50vt%3DiNDaJLmsVCbQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/CAPxKSaH1Sk2OEYm0Ri8zZdxemgKb1PX3DbhdRgc8Prrq4esR2A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
