On Thu 31 Aug 2017 at 16:41, Steven Foster <stevengfos...@gmail.com> wrote:
> Hi, > > Multibranch pipeline jobs do not automatically configure Github webhooks, > right? > It's necessary to set up the Jenkins (github plugin) service on the Github > repo and add the Jenkins user as a collaborator? > > Just wanted to make sure my understanding was correct before I give people > the wrong advice. > Sigh! So right now the organisation-level hooks are managed by GHBS plugin The repository level hooks are managed by the GH plugin and the GHBS plugin has the correct extensions to tell the GH plugin that it needs hooks managed... Ultimately we want all the hooks managed in the one place, but not there yet... History: Now as the GH plugin is actively managing the repo-level hooks, we have to delegate to that from the GHBS plugin otherwise the two plugins will end up fighting it out and toggling hooks on and off, hence why the repo level hooks are managed by GH plugin. As the GH plugin doesn't manage organisation levels hooks, in the GHBS plugin we took the "quick" route of managing org level hooks there. So... what does that mean? Well what it means is that to have hooks automatically managed at the repo level you need to define the GitHub servers in the global config, enable managing hooks and provide credentials that can manage hooks (note this is the list provided by the GH plugin, not to be confused with the github enterprise servers list in the global config that is provided by the GHBS plugin) Of course the credentials needed are not the correct type (secret text, should be a GitHub specific credentials type) and none of this is obvious... And rtyler seems to think that it doesn't work anyway... but *in theory* - right now - that is what you are supposed to do and if you do that it works - at least every time I have tried it! There are plans to consolidate the servers list and switch from secret text to a GitHub specific credentials type... but that's probably a couple of months given the migration testing that would be required. HTH > > -- > 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 jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/935e1006-e2ae-4215-9798-ab5f1e8152cc%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/935e1006-e2ae-4215-9798-ab5f1e8152cc%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Sent from my phone -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMwRvo7StoR2pQr-fu-XvM7yyyRbZW83zEGygs3cE6gbmQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
