[
https://issues.jenkins-ci.org/browse/JENKINS-10405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163227#comment-163227
]
David Beitey commented on JENKINS-10405:
----------------------------------------
So my projects on Jenkins were configured correctly with WebHook URLs in Github
and they've suddenly stopped building when the POST requests come in. This
might either be because I've upgrade to Jenkins 1.456 or upgraded to github-api
1.25 (using version 1.2 of GitHub Plugin). Either way, the POSTs are accepted
by Jenkins and the logger I've configured displays the following output:
May 28, 2012 4:04:36 PM com.cloudbees.jenkins.GitHubWebHook
FINE: Skipped my.project because it doesn't have a matching repository.
May 28, 2012 4:04:36 PM com.cloudbees.jenkins.GitHubWebHook
FINE: Full details of the POST was {<snip out long GitHub post details>}
May 28, 2012 4:04:36 PM com.cloudbees.jenkins.GitHubWebHook processGitHubPayload
INFO: Received POST for https://github.com/davidjb/profiles.project
and that's the end of the logs. No builds actually happen.
As mentioned, everything was working fine, so URLs for source repos are okay.
Anyone seeing the same?
> Post-receive hook doesn't work
> ------------------------------
>
> Key: JENKINS-10405
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10405
> Project: Jenkins
> Issue Type: Bug
> Components: github
> Affects Versions: current
> Environment: 64-bit Ubuntu Maverick server, Sun Java 6 JVM, official
> .debs.
> Reporter: ieure
> Assignee: Kevin Sawicki
> Attachments: security-settings.png
>
>
> I configured GitHub's web hooks for a project and pushed code, but the job
> didn't build. I captured the payload with PostBin:
> http://www.postbin.org/sq1n8a ; then sent it with Curl to see what was going
> on:
> curl -k -H 'Content-Type: application/x-www-form-urlencoded' -XPOST
> https://ci.public.simplegeo.com/github-webhook/ -d...@x.js
> I received this stacktrace in response: https://gist.github.com/1095538
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
