[JIRA] [github-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Title: Message Title Dmytro Kryvenko edited a comment on JENKINS-27282 Re: Github Webhook not working after upgrade Jenkins and plugins UPD: It is also works fine with refs/heads/master if "Force polling using workspace" is enabled. Looks like a Jenkins Core regression. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [github-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Title: Message Title Dmytro Kryvenko commented on JENKINS-27282 Re: Github Webhook not working after upgrade Jenkins and plugins UPD: It is also works fine with refs/heads/master if "Force polling using workspace" is enabled. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [github-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Title: Message Title Dmytro Kryvenko edited a comment on JENKINS-27282 Re: Github Webhook not working after upgrade Jenkins and plugins Ran into this issue as well after recently upgraded Jenkins (always using stable only).Git plugin 2.3.5GitHub API plugin 1.68GitHub plugin 1.11.3Jenkins 1.609.1GitHub Enterprise 11.10.348 In the logs I can see that all required jobs are "poked", but nothing happens after that pokes.Repro steps:1. Create new freestyle project2. Setup SCM as Git to pointing some repo3. Change Branch Specifier from */master to refs/heads/master4. Add GitHub web-hook5. Push commit to the repoNote that it works fine with */master as a branch settings. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [github-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Title: Message Title Dmytro Kryvenko commented on JENKINS-27282 Re: Github Webhook not working after upgrade Jenkins and plugins Ran into this issue as well after recently upgraded Jenkins (always using stable only). Git plugin 2.3.5 GitHub API plugin 1.68 GitHub plugin 1.11.3 Jenkins 1.609.1 GitHub In the logs I can see that all required jobs are "poked", but nothing happens after that pokes. Repro steps: 1. Create new freestyle project 2. Setup SCM as Git to pointing some repo 3. Change Branch Specifier from */master to refs/heads/master 4. Add GitHub web-hook 5. Push commit to the repo Note that it works fine with */master as a branch settings. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [github-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Harrison Powers commented on JENKINS-27282 Github Webhook not working after upgrade Jenkins and plugins @Alexandre that fixed it for me. Thanks! 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/d/optout.
[JIRA] [github-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Anant Narayanan commented on JENKINS-27282 Github Webhook not working after upgrade Jenkins and plugins @Alexandre Yes, but I do not have the EnvInject plugin installed at all! 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/d/optout.
[JIRA] [github-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Alexandre Zia commented on JENKINS-27282 Github Webhook not working after upgrade Jenkins and plugins @Anant for this error "ERROR: Failed to record SCM polling" you can downgrade EnvInject Plugin to 1.90 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/d/optout.
[JIRA] [github-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Anant Narayanan edited a comment on JENKINS-27282 Github Webhook not working after upgrade Jenkins and plugins I have the same problem with Jenkins 1.600 and 1.601, but with a slightly different error in the "Github Hook Log". I do not have the EnvInject plugin installed. Using strategy: Default [poll] Last Built Revision: Revision 11aa79761c883cceac79c26ff8b6f5f777d80965 (refs/remotes/origin/master) > git --version # timeout=10 > git -c core.askpass=true ls-remote -h g...@github.com:anantn/myrepo.git # timeout=10 ERROR: Failed to record SCM polling org.eclipse.jgit.errors.InvalidObjectIdException: Invalid id : Process leaked file descriptors. See htt at org.eclipse.jgit.lib.ObjectId.fromHexString(ObjectId.java:245) at org.eclipse.jgit.lib.ObjectId.fromString(ObjectId.java:233) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getHeadRev(CliGitAPIImpl.java:2333) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:576) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:526) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:380) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject._poll(AbstractProject.java:1446) at hudson.model.AbstractProject.poll(AbstractProject.java:1349) at com.cloudbees.jenkins.GitHubPushTrigger$1.runPolling(GitHubPushTrigger.java:81) at com.cloudbees.jenkins.GitHubPushTrigger$1.run(GitHubPushTrigger.java:106) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) 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/d/optout.
[JIRA] [github-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Anant Narayanan commented on JENKINS-27282 Github Webhook not working after upgrade Jenkins and plugins I have the same problem with Jenkins 1.600 and 1.601, but with a slightly different error in the "Github Hook Log": Using strategy: Default [poll] Last Built Revision: Revision 11aa79761c883cceac79c26ff8b6f5f777d80965 (refs/remotes/origin/master) > git --version # timeout=10 > git -c core.askpass=true ls-remote -h g...@github.com:anantn/myrepo.git # timeout=10 ERROR: Failed to record SCM polling org.eclipse.jgit.errors.InvalidObjectIdException: Invalid id : Process leaked file descriptors. See htt at org.eclipse.jgit.lib.ObjectId.fromHexString(ObjectId.java:245) at org.eclipse.jgit.lib.ObjectId.fromString(ObjectId.java:233) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getHeadRev(CliGitAPIImpl.java:2333) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:576) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:526) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:380) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject._poll(AbstractProject.java:1446) at hudson.model.AbstractProject.poll(AbstractProject.java:1349) at com.cloudbees.jenkins.GitHubPushTrigger$1.runPolling(GitHubPushTrigger.java:81) at com.cloudbees.jenkins.GitHubPushTrigger$1.run(GitHubPushTrigger.java:106) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) 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/d/optout.
[JIRA] [github-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Alexandre Zia
commented on JENKINS-27282
Github Webhook not working after upgrade Jenkins and plugins
Update:
I'm using EnvInject plugin, and set "Prepare an environment for the run", then setting several varibles in "Properties Content" like: GIT_BRANCH=dev
Then in git configuration, in "Branches to build" I'm using the variable: refs/heads/${GIT_BRANCH}
That always worked.
So I've tested several ways, without sucess:
refs/heads/${GIT_BRANCH}
refs/heads/$GIT_BRANCH
*/${GIT_BRANCH}
*/$GIT_BRANCH
I just tried removing the variable and set it hardcoded:
refs/heads/dev => not worked
And then, simply:
dev
*/dev
then it worked, any of the two combinations above, without varaibles and without specifying
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/d/optout.
[JIRA] [github-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Alexandre Zia commented on JENKINS-27282 Github Webhook not working after upgrade Jenkins and plugins Thanks for the hint. I've upgraded Jenkins to 1.602 and downgraded envinject to 1.90 Now there is no backtrace, but no build also __ GitHubWebHook log : Mar 09, 2015 7:05:21 PM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayload Received POST for https://github.com/MyCompany/MyJob Mar 09, 2015 7:05:21 PM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayload Poked MyJob Mar 09, 2015 7:05:21 PM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayload __ GitHub Hook Log Last GitHub Push Started on Mar 9, 2015 7:09:08 PM Using strategy: Default [poll] Last Built Revision: Revision 6fa1b84438478b04d1fc8b5de9180b0e65ad8acb (refs/remotes/origin/dev) > git --version # timeout=10 > git -c core.askpass=true ls-remote -h g...@github.com:MyCompany/MyRepos.git # timeout=10 Done. Took 0.92 sec No changes __ Whenever my Jenkins receives a github webhook it updates Github Hook Log date, so I'm considering thar the webhook from github is firing a poll in my repository to check for new commits in my repository. However my repository on github is not on this Revision, it is several commits ahead, but when Jenkins receives the Github webhook it runs thius check and don't actually see the real position in guthub Regards Alexandre 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/d/optout.
[JIRA] [github-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Cezar Espinola commented on JENKINS-27282 Github Webhook not working after upgrade Jenkins and plugins I also had the same problem with Git plugin. A workaround for me was downgrading EnvInject plugin to 1.90, everything works now. 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/d/optout.
[JIRA] [github-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Alexandre Zia created JENKINS-27282 Github Webhook not working after upgrade Jenkins and plugins Issue Type: Bug Assignee: Unassigned Components: github-plugin Created: 08/Mar/15 7:13 PM Description: When github sends a webhook to trigger a build in Jenkins, the Job does not start. I've already downgraded Jenkins and github plugin back to original versions but the issue persists. I've also wiped the workspace and started an initial build manually, and the issue persists Adding the logger: "com.cloudbees.jenkins.GitHubWebHook" I can see this stacktrace: Mar 08, 2015 6:29:57 PM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayload Received POST for https://github.com/MyCompany/MyRepository Mar 08, 2015 6:29:57 PM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayload Poked MyJob Mar 08, 2015 6:29:57 PM SEVERE com.cloudbees.jenkins.GitHubPushTrigger$1 runPolling Failed to record SCM polling java.lang.NullPointerException at org.jenkinsci.plugins.envinject.EnvInjectPluginAction$1.transformEntry(EnvInjectPluginAction.java:25) at org.jenkinsci.plugins.envinject.EnvInjectPluginAction$1.transformEntry(EnvInjectPluginAction.java:23) at com.google.common.collect.Maps$TransformedEntriesMap$1$1.apply(Maps.java:1218) at com.google.common.collect.Maps$TransformedEntriesMap$1$1.apply(Maps.java:1216) at com.google.common.collect.Iterators$8.next(Iterators.java:812) at java.util.AbstractMap.putAll(AbstractMap.java:272) at java.util.TreeMap.putAll(TreeMap.java:321) at org.jenkinsci.plugins.envinject.EnvInjectVarList.(EnvInjectVarList.java:26) at org.jenkinsci.plugins.envinject.EnvInjectPluginAction.getTarget(EnvInjectPluginAction.java:22) at org.jenkinsci.plugins.envinject.EnvInjectPluginAction.buildEnvVars(EnvInjectPluginAction.java:31) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:929) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:564) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:526) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:380) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject._poll(AbstractProject.java:1446) at hudson.model.AbstractProject.poll(AbstractProject.java:1349) at com.cloudbees.jenkins.GitHubPushTrigger$1.runPolling(GitHubPushTrigger.java:81) at com.cloudbees.jenkins.GitHubPushTrigger$1.run(GitHubPushTrigger.java:106) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679)Mar 08, 2015 6:29:57 PM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayload Environment: Latest Jenkins 1.601 but hte issue had appeared in 1.600 Project: Jenkins Priority: Major Reporter: Alexandre Zia 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
