On Wednesday, November 22, 2017 at 10:50:52 AM UTC-5, Stephen Connolly wrote: > > >>> * The Jenkinsfile for both branches is the same (v1.14 is a branch of >>> master) and has the following setup for triggering with a github push: >>> >>> properties([ >>> pipelineTriggers([triggers: [[$class: "GitHubPushTrigger"]]]) >>> ]) >>> >> >> Dont do that. >> >> Multibranch is opinionated, if you have set up your webhook correctly, >> you are done. That config is what is causing your issue. >> > > To clarify, multibranch automatically detects those push events and > handles them automatically. > Well, I only added it after I couldn't get commits to trigger builds to start with. From some Googling, I saw some folks using that so I thought it was required to trigger it on push events.
But I tried it now just to be sure. I removed it, deleted the job and rebuilt it from scratch, and now the job won't trigger at all on commits. I re-configured my webhooks (they are set at the Organization level ... I tried them at the repository level as well and it didn't work either.) I can't find a webhook log now either ... although I see the event being received in my log: Nov 22, 2017 5:13:53 PM org.jenkinsci.plugins.github_branch_source.PushGHEventSubscriber onEvent INFO: Received PUSH for https://github.com/FakeOrg/FakeRepo from x.x.x.x ⇒ https://fake.hostname/github-webhook/ Is that the right webhook event handler? There's so many of them I can't tell if one plugin is affecting another. -- 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/03c8d982-8d92-464c-ae1d-4052d639d3b7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
