[JIRA] [git-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Title: Message Title Dmytro Kryvenko resolved as Fixed Jenkins 1.609.1 git plugin 2.4.0 Confirm that the issue has been resolved. Tests done: 1. Created freestyle project 2. Added Git SCM configuration with the branch "refs/heads/master" value 3. Checkbox enabled "Build when a change is pushed to github" 4. Verified few times that the job is triggered per push to github Jenkins / JENKINS-27282 Github Webhook not working after upgrade Jenkins and plugins Change By: Dmytro Kryvenko Status: Open Resolved Resolution: Fixed 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] [git-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 From the Jenkins :) https://jenkins.ci.cloudbees.com/job/plugins/job/git-plugin/ws/target/git.hpi But this is a CI build, personally I wouldn't recommend you to use it on a production Jenkins instance... 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] [git-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 From the Jenkins https://jenkins.ci.cloudbees.com/job/plugins/job/git-plugin/ws/target/git.hpi 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] [git-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Title: Message Title Dmytro Kryvenko updated an issue Jenkins / JENKINS-27282 Github Webhook not working after upgrade Jenkins and plugins Change By: Dmytro Kryvenko Component/s: core 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] [git-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 Mark Waite, I've checked with latest https://jenkins.ci.cloudbees.com/job/plugins/job/git-plugin/829/ build, the issue is not reproducible anymore. Looking forward to have new git-plugin available in stable! Liya Katz, most probably issue was caused by core change, but it's not explicitly tell us this is a core issue. I've looked into a core code first, and buggy method realization is in git-plugin. So that's pure git-plugin issue, that is already fixed and tested, we should just wait for a next git-plugin release. 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] [git-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Title: Message Title Dmytro Kryvenko updated an issue Jenkins / JENKINS-27282 Github Webhook not working after upgrade Jenkins and plugins Change By: Dmytro Kryvenko Component/s: core 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] [core] (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: This issue caused by one of this issues: JENKINS-28506 or JENKINS-27332 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] [core] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Title: Message Title Dmytro Kryvenko updated an issue Jenkins / JENKINS-27282 Github Webhook not working after upgrade Jenkins and plugins Change By: Dmytro Kryvenko Component/s: git-plugin 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] [core] (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 or git-plugin 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] [core] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Title: Message Title Dmytro Kryvenko updated an issue Jenkins / JENKINS-27282 Github Webhook not working after upgrade Jenkins and plugins Change By: Dmytro Kryvenko Component/s: core 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 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-22578) Nothing happens when POST to jenkins github-webhook url
Title: Message Title Dmytro Kryvenko commented on JENKINS-22578 Re: Nothing happens when POST to jenkins github-webhook url This is a duplicate for JENKINS-27282 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] [delivery-pipeline-plugin] (JENKINS-26726) java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70)
Dmytro Kryvenko closed JENKINS-26726 as Cannot Reproduce java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70) Change By: Dmytro Kryvenko (14/Apr/15 2:15 PM) Status: Open Closed Resolution: Cannot Reproduce 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] [delivery-pipeline-plugin] (JENKINS-26726) java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70)
Dmytro Kryvenko commented on JENKINS-26726 java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70) Sorry for a delay. I was trying to reproduce this one again with no luck. It seems like a 3rd party plugin caused this behaviour originally and probably it has been fixed on their side. Closing this issue for now, will reopen in case of luck with reproducing. 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] [delivery-pipeline-plugin] (JENKINS-26726) java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70)
Dmytro Kryvenko created JENKINS-26726 java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70) Issue Type: Bug Assignee: Dmytro Kryvenko Components: delivery-pipeline-plugin Created: 02/Feb/15 2:24 AM Description: Steps to reproduce: 1. Create jobs A, B and C 2. C should be a downstream job for both A and B 3. A and B doesn't have direct relations 4. Create two Delivery Pipeline instances pA and pB (starting from A and B jobs accordingly) 5. Run job A and wait for finish job C 6. Rebuild job A and wait again 7. Run job B and open pB pipeline in browser - you will see Server Error 8. In the meantime Jenkins log will contains following error: WARNING: Error while serving https://jenkins.myorg.com/view/pB/api/json java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor487.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.service(Stapler.java:237) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:198) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:176) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:99) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
