Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

WebHook recieved but not triggering event.

See original GitHub issue

Webhook set for github repository and the receiving 200 back from jenkins server. Logs look like this:

Mar 04, 2016 8:16:48 AM org.jenkinsci.plugins.ghprb.GhprbWebHook checkSignature INFO: Signatures checking OK Mar 04, 2016 8:16:48 AM org.jenkinsci.plugins.ghprb.GhprbWebHook handleWebHook INFO: Got payload event: push Mar 04, 2016 8:16:48 AM org.jenkinsci.plugins.ghprb.GhprbWebHook handleWebHook WARNING: Request not known Mar 04, 2016 8:16:48 AM org.jenkinsci.plugins.ghprb.GhprbWebHook checkSignature INFO: Signatures checking OK Mar 04, 2016 8:16:48 AM org.jenkinsci.plugins.ghprb.GhprbWebHook handleWebHook INFO: Got payload event: push Mar 04, 2016 8:16:48 AM org.jenkinsci.plugins.ghprb.GhprbWebHook handleWebHook WARNING: Request not known Mar 04, 2016 8:16:48 AM org.jenkinsci.plugins.ghprb.GhprbWebHook checkSignature INFO: Signatures checking OK Mar 04, 2016 8:16:48 AM org.jenkinsci.plugins.ghprb.GhprbWebHook handleWebHook INFO: Got payload event: push Mar 04, 2016 8:16:48 AM org.jenkinsci.plugins.ghprb.GhprbWebHook handleWebHook WARNING: Request not known

Have another project with the exact same configurations and this is what the logs look like for it. Mar 04, 2016 8:13:03 AM org.jenkinsci.plugins.ghprb.GhprbWebHook checkSignature INFO: Signatures checking OK Mar 04, 2016 8:13:03 AM org.jenkinsci.plugins.ghprb.GhprbWebHook handleWebHook INFO: Got payload event: push Mar 04, 2016 8:13:03 AM org.jenkinsci.plugins.ghprb.GhprbWebHook handleWebHook WARNING: Request not known Mar 04, 2016 8:13:03 AM org.jenkinsci.plugins.ghprb.GhprbWebHook checkSignature INFO: Signatures checking OK Mar 04, 2016 8:13:03 AM org.jenkinsci.plugins.ghprb.GhprbWebHook handleWebHook INFO: Got payload event: push Mar 04, 2016 8:13:03 AM org.jenkinsci.plugins.ghprb.GhprbWebHook handleWebHook WARNING: Request not known Mar 04, 2016 8:13:03 AM org.jenkinsci.plugins.ghprb.GhprbWebHook checkSignature INFO: Signatures checking OK Mar 04, 2016 8:13:03 AM org.jenkinsci.plugins.ghprb.GhprbWebHook handleWebHook INFO: Got payload event: push Mar 04, 2016 8:13:03 AM org.jenkinsci.plugins.ghprb.GhprbWebHook handleWebHook WARNING: Request not known Mar 04, 2016 8:13:03 AM org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber onEvent INFO: Received POST for https://github.com/OdenTech/oden_dal Mar 04, 2016 8:13:03 AM org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber$1 run INFO: Poked DevOdenDal Mar 04, 2016 8:13:03 AM org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber$1 run INFO: Poked OdenDal Mar 04, 2016 8:13:04 AM com.cloudbees.jenkins.GitHubPushTrigger$1 run INFO: SCM changes detected in DevOdenDal. Triggering #457 Mar 04, 2016 8:13:12 AM jenkins.plugins.slack.SlackNotifier$SlackJobProperty prebuild INFO: Invoking Started... Mar 04, 2016 8:13:12 AM jenkins.plugins.slack.ActiveNotifier getChanges INFO: Entry hudson.plugins.git.GitChangeSet@8584ed66 Mar 04, 2016 8:13:12 AM jenkins.plugins.slack.StandardSlackService publish INFO: Posting: to #engineering on odentech using https://odentech.slack.com/services/hooks/jenkins-ci?token=F4m37RrBsfd9myItg0J4IA4B: DevOdenDal - #457 Started by changes from sam.flint (1 file(s) changed) (<http://github-jenkins-652346236.us-west-2.elb.amazonaws.com/job/DevOdenDal/457/|Open>) good Mar 04, 2016 8:13:12 AM jenkins.plugins.slack.StandardSlackService publish INFO: Posting succeeded Mar 04, 2016 8:13:25 AM hudson.model.Run execute INFO: DevOdenDal #457 main build action completed: SUCCESS Mar 04, 2016 8:13:25 AM jenkins.plugins.slack.StandardSlackService publish INFO: Posting: to #engineering on odentech using https://odentech.slack.com/services/hooks/jenkins-ci?token=F4m37RrBsfd9myItg0J4IA4B: DevOdenDal - #457 Success after 15 sec (<http://github-jenkins-652346236.us-west-2.elb.amazonaws.com/job/DevOdenDal/457/|Open>) No Tests found. good Mar 04, 2016 8:13:26 AM jenkins.plugins.slack.StandardSlackService publish INFO: Posting succeeded

The differences start with : org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber onEvent INFO: Received POST for https://github.com/OdenTech/oden_dal

I am not sure what is looking for this event but I also compared the payloads from github and they look identical except for the repo names and etc. I have the “Build when a change is pushed to GitHub” checked for both of these projects. The only difference I can see between them is the GitHub project name.

Issue Analytics

State:
Created 8 years ago
Comments:7 (2 by maintainers)

Top GitHub Comments

2reactions

EniariGamescommented, Feb 17, 2019

I’m having the same issues

1reaction

xkcodingcommented, Mar 1, 2019

I’m having the same issues

Top Results From Across the Web

Jenkins: Github webhook does not trigger any job

Check your Jenkins logs to see whether or not Jenkins is receiving the hook and deciding not to take action for some reason....

GitHub: Webhook Troubleshooting - CloudBees Support

Jobs are not automatically triggered when after a Push or Pull request ... In case the webhook was sucessfully, Jenkins receives a PING...

Complete Guide to Troubleshooting and Debugging Webhooks

The first thing you want to be sure of is that you are receiving your webhooks. Because webhooks are regular HTTP requests originating...

Gitlab webhooks does not trigger (#350636) · Issues

Webhooks on my gitlab server does not works when an event is created but when i test the webhook it launchs the job...

Setting up webhooks to trigger event notifications - Replicon

Webhooks notifications have many potential uses, especially in providing automated notification, and in integrations with third-party apps. They provide an ...