[JIRA] (JENKINS-10405) Post-receive hook doesn't work

[irist...@java.net (JIRA)]

Iristyle edited a comment on JENKINS-10405 Post-receive hook doesn't work I can confirm the same issue with GitHub OAuth enabled. It appears the crux of this issue is when non-standard Jenkins authentication methods are being used. Not even sure you can work around this here – but some notes in the docs might be helpful. What I tried to do, based on above comments was Change the 'Override Hook URL' for the 'GitHub Web Hook' to use https://user:to...@buildserver.com/github-webhook/ (this only affects new projects) Created a new job, pointed it at a GitHub repo – the hook was properly registered at GitHub with the updated url style, so at least that part is working. However, it still didn't work when clicking test. So I followed the above recommendations: Remove the 'Jenkins (GitHub plugin)' service hook that looks like https://user:to...@buildserver.com/github-webhook/ Add a new 'WebHook URL' service hook with a url like https://user:to...@buildserver.com/github-webhook/ Note that the user / token is this case is the GitHub user account as well. It would appear that the missing piece to making this work is to update the hook on the GitHub side to handle the credentials properly like 'WebHook URL' does. Note that I also built a custom version of the GitHub-OAuth plugin that fixed the Basic Auth API. They fixed the bug a couple of months ago, but never released an updated plugin, which is a real shame. https://github.com/mocleiri/github-oauth-plugin/commits/master

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira