[JIRA] (JENKINS-10405) Post-receive hook doesn't work
Kevin Fleming commented on JENKINS-10405 Post-receive hook doesn't work I too just ran into this issue, and while I'm not using any authentication that got in the way, I did have to change the repository URLs in my jobs to end with ".git" in order for the Webhook-provided URL to be matched up. Once I made this change I was able to use the 'Jenkins (GitHub plugin)' service hook in GitHub just fine. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10405) Post-receive hook doesn't work
Dave Abrahams commented on JENKINS-10405 Post-receive hook doesn't work One critical thing: make sure the github project is identified to the plugin with its https:// URL, i.e. don't forget the "s". Even though Github will redirect you there from "http://", the plugin needs to see the exact URL reported by the webhook. 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
[JIRA] (JENKINS-10405) Post-receive hook doesn't work
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
[JIRA] (JENKINS-10405) Post-receive hook doesn't work
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 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 new style url did persist at GitHub, so that part is working. However, it still didn't work. So I followed the above notes – 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/` 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. 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
[JIRA] (JENKINS-10405) Post-receive hook doesn't work
Iristyle commented 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 – but some notes in the docs might be helpful. I should note that the solution was the same for me – Remove the 'Jenkins (GitHub plugin)' service hook Add a new 'WebHook URL' service hook with a url like https://user:to...@buildserver.com/github-webhook/ I also tried using the above url as the 'Jenkins (GitHub plugin)' url and it did not work. Furthermore, I did check the box to 'Override Hook URL' for the 'GitHub Web Hook' configuration for Jenkins – with the same url. Setting that url part worked properly, so it seems 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. 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
[JIRA] (JENKINS-10405) Post-receive hook doesn't work
Lars Bilke commented on JENKINS-10405 Post-receive hook doesn't work I have also setup a logger which outputs this on every push to GitHub: Sep 5, 2012 12:21:34 PM com.cloudbees.jenkins.GitHubWebHook processGitHubPayload INFO: Received POST for https://github.com/ufz/ogs But unfortunately no build is triggered. I am using the latest Jenkins and GitHub-plugin. 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
[JIRA] (JENKINS-10405) Post-receive hook doesn't work
Jonathan Vaughn edited a comment on JENKINS-10405 Post-receive hook doesn't work We have also encountered an issue with permissions (403 response to POST on the webhook URL) using LDAP security, as lesterp commented on 12/27/2011. We are using Matrix-based security with users and groups in LDAP. We were able to work around it by giving anonymous users Overall read access, however ideally there should be some way to grant github read access without giving anonymous users github access, and preferably without having to create a dummy github account in LDAP (is that an option even? where do we tell github what password to use?). Also, if it makes any difference, we're running on CentOS6 x86_64. 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
[JIRA] (JENKINS-10405) Post-receive hook doesn't work
Jonathan Vaughn commented on JENKINS-10405 Post-receive hook doesn't work We have also encountered an issue with permissions (403 response to POST on the webhook URL) using LDAP security, as lesterp commented on 12/27/2011. We are using Matrix-based security with users and groups in LDAP. We were able to work around it by giving anonymous users Overall read access, however ideally there should be some way to grant github read access without giving anonymous users github access, and preferably without having to create a dummy github account in LDAP (is that an option even? where do we tell github what password to use?). 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
[JIRA] (JENKINS-10405) Post-receive hook doesn't work
David Beitey
edited a comment on JENKINS-10405
Post-receive hook doesn't work
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 {}
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?
Edit: tested with github-api 1.23 and still no good.
Edit2: It is working again for me under Jenkins 1.470 and github-api 1.28 and GitHub plugin 1.4.
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
[JIRA] (JENKINS-10405) Post-receive hook doesn't work
[
https://issues.jenkins-ci.org/browse/JENKINS-10405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163227#comment-163227
]
David Beitey edited comment on JENKINS-10405 at 5/28/12 6:20 AM:
-
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 {}
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?
Edit: tested with github-api 1.23 and still no good.
was (Author: davidjb):
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 {}
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
[JIRA] (JENKINS-10405) Post-receive hook doesn't work
[
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 {}
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
[JIRA] (JENKINS-10405) Post-receive hook doesn't work
[ https://issues.jenkins-ci.org/browse/JENKINS-10405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162739#comment-162739 ] asher newcomer commented on JENKINS-10405: -- I wasted a few hours on this before stumbling across Chris' comment above. I can confirm that this all works fine, even with HTTPS and Active Directory authentication in Jenkins. You just need to be sure *NOT* to use the specific Jenkins(GitHub plugin) webhook in Github, and rather choose the generic one. > 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
[JIRA] (JENKINS-10405) Post-receive hook doesn't work
[ https://issues.jenkins-ci.org/browse/JENKINS-10405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162677#comment-162677 ] Chris Heng commented on JENKINS-10405: -- I had the same problem -- I followed the instructions by Tim Linquist, but the Jenkins job was simply not recognizing the POST from GitHub. Finally I managed to get it working. The trick is to put your github-webhook URL (HTTP basic auth and all) in "Webhook URLs" (the first item in the GitHub service hooks list), *NOT* "Jenkins (GitHub plugin)". > 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
[JIRA] (JENKINS-10405) Post-receive hook doesn't work
[ https://issues.jenkins-ci.org/browse/JENKINS-10405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162193#comment-162193 ] David Kennedy commented on JENKINS-10405: - I have hit this issue from an upgrade from Ubuntu 10.04 to Ubuntu 11.10, using the dist's version of Jenkins. (We had to upgrade due to a MySQL 5.1 -> 5.5 issue) Previous to the upgrade webhooks worked fine, afterward they do not. Downgrading the version of the plugin to 0.7 as before did not help. We've had to revert to SCM polling, which sucks for us and for GitHub. The 'debuggability' of this issue is very low and it leads to a lot of frustration in figuring out the issue - the advice above did not solve my issue, the regex should match fine for our projects. The regex does not match the help text in the UI. > 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
