![]() |
|
|
Issue Type:
|
Bug
|
Affects Versions:
|
current |
Assignee:
|
Honza Brázdil
|
Components:
|
ghprb |
Created:
|
08/May/13 5:31 PM
|
Description:
|
Just upgraded to v1.8 from 1.5.1.
We decided to change from the cron to using the hook/callback. It worked fine when comments were added such as "retest this please" (issue_comment hook), but when a new commit is pushed (pull_request hook, synchronize action), it isn't triggering a new build. Closing and opening the pull request does trigger a new build.
I checked the logs and there seems to be a null pointer exception. I haven't had time to really debug it any further yet.
Also, randomly after closing/reopening, adding/deleting some comments, etc... It started telling me that the pull request that the hook was being triggered for didn't exist.
Everything appears to be working by simply switching back to the cron strategy (unchecking "Use github hooks for build triggering") for now.
Once I finish some other work, I'll switch it back to the hook method and try to debug further.
|
Project:
|
Jenkins
|
Priority:
|
Major
|
Reporter:
|
Evan Coury
|
|
|
|
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.