Figured out the issue.
In order to manage Webhooks, the branch job must have:
a. run at least once
b. contain at least one scm checkout
In my simple testing neither of those cases were true, leading me to go
round in circles for awhile :)
I suspect the request to manage from the branch source pl
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 s
On Friday, September 1, 2017 at 12:18:35 AM UTC+1, Stephen Connolly wrote:
>
>
> 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 (
On Thu 31 Aug 2017 at 16:41, Steven Foster 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 su
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
