On Friday, September 1, 2017 at 11:57:32 AM UTC+1, Stephen Connolly wrote: > > The credentials provided for manage hooks needs to have permission to > manage hooks on all repositories. > > You may need to trigger the "Re-register hooks for all jobs" if something > went wrong. > > HTH >
Still struggling with this. I'm continuing testing on a dedicated Jenkins for figuring this out in a small, reproducible way before rolling it out to a user with org-wide permissions. My repositories are in GitHub enterprise, private under my user (so not an organization). The credential provided to GitHub global config is secret text of a key from my personal user with *admin:org_hook, admin:repo_hook, repo *permissions. The credential works with Test Connection. The credentials given to the multibranch job configuration are my GitHub username and password credentials. In the Jenkins system log I see "GitHub webhooks activated for job webhook with [] (events: [PULL_REQUEST, PUSH])" In GitHub I don't see any webhooks set up in the repo settings, and the job doesn't respond to push events. Going through with a debugger near that log event (GithubPlugin WebhookManager, registerFor) it seems like the repository name is not being mapped from the multibranch job (it's not an SCMTriggerItem). You'll know how this works better than I do, maybe this process is irrelevant and the log event doesn't apply here. Is there anywhere else I can run with a debugger that might help? -- 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/e46349c5-b25b-4687-9c2c-463c4fe78c02%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
