Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Jenkins job was poked by a GitHub webhook but didn't start

I am running GHE 2.3.1 in private mode (anonymous cloning and repo browsing is not allowed in my organization) and we use Jenkins for CI. Before I put GHE into private mode I could have Jenkins fire jobs for repos when push events happen, using webhooks. After I set private mode this no longer happens.

In Jenkins I see that the webhook was received but the job didn't start.

Sep 23, 2015 4:13:35 PM INFO org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber onEvent
Received POST for http://github.company.com/org/repo
Sep 23, 2015 4:13:35 PM INFO org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber$1 run
Poked Job Name - build master

My job has no history of starting and failing. This is true for all jobs relying on push hooks. However, my jobs that run on pull request hooks are working, so I'm not sure what's wrong.

Any ideas?

like image 736
Tyler Smith Avatar asked Sep 23 '15 21:09

Tyler Smith


People also ask

How does Jenkins and GitHub webhook work?

Jenkins GitHub Webhook is used to trigger the action whenever Developers commit something into the repository. It can automatically compile or deploy applications if there are no errors detected.


1 Answers

Turns out there was an error in the GitHub Hook log that pointed me to the version of Git installed on the Jenkins master server. After updating it to the newest version the error went away and jobs started to build on hooks again.

like image 114
Tyler Smith Avatar answered Sep 21 '22 14:09

Tyler Smith