[JIRA] [core] (JENKINS-28955) Jenkins unusable after downgrade from latest weekly release to LTS
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-28955 Jenkins unusable after downgrade from latest weekly release to LTS Change By: Jesse Glick Status: Reopened Resolved Resolution: Duplicate 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-28955) Jenkins unusable after downgrade from latest weekly release to LTS
Title: Message Title Jesse Glick commented on JENKINS-28955 Re: Jenkins unusable after downgrade from latest weekly release to LTS Sounds like a duplicate of JENKINS-21486, no? 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-28955) Jenkins unusable after downgrade from latest weekly release to LTS
Title: Message Title Vincent Latombe commented on JENKINS-28955 Re: Jenkins unusable after downgrade from latest weekly release to LTS Submitted https://github.com/jenkinsci/jenkins/pull/2172 to disable plugins whose dependencies are obsolete, which should allow Jenkins to successfully boot without the faulty plugins. 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-28955) Jenkins unusable after downgrade from latest weekly release to LTS
Title: Message Title Vincent Latombe commented on JENKINS-28955 Re: Jenkins unusable after downgrade from latest weekly release to LTS Hit that problem as well. To me the crux of the issue is that plugins dependency checking doesn't verify required versions, it only checks if dependencies are installed. Then comes the Extension phase and everything blows up because extensions of all loaded plugins are loaded at the same time and we can't disable faulty plugins anymore. I think it would be much safer to just disable plugins for which dependencies are outdated. 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-28955) Jenkins unusable after downgrade from latest weekly release to LTS
Title: Message Title Oleg Nenashev commented on JENKINS-28955 Re: Jenkins unusable after downgrade from latest weekly release to LTS Got into the issue as well. In my case it happens due to the fatal GuiceFinder initialization issue on the startup. It has been caused by a closed-source plugin in my case, but there are potential causes in other plugins and the Jenkins core. Oct 09, 2015 8:00:04 PM hudson.ExtensionFinder$GuiceFinder SEVERE: Failed to create Guice container from all the plugins com.google.inject.CreationException: Guice creation errors: 1) No implementation for r was bound. while locating for parameter 0 at Y.(Feeder.java:61) while locating ZZZ for field at ZZ at ZZZ 1 error at com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:448) at com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:155) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107) at com.google.inject.Guice.createInjector(Guice.java:96) at com.google.inject.Guice.createInjector(Guice.java:73) at hudson.ExtensionFinder$GuiceFinder.(ExtensionFinder.java:280) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:422) at java.lang.Class.newInstance(Class.java:442) at net.java.sezpoz.IndexItem.instance(IndexItem.java:181) at hudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:643) at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:618) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:388) at hudson.ExtensionList.load(ExtensionList.java:349) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:287) at hudson.ExtensionList.iterator(ExtensionList.java:156) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:381) at hudson.ExtensionList.load(ExtensionList.java:349) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:287) at hudson.ExtensionList.get(ExtensionList.java:171) at hudson.PluginManager$PluginUpdateMonitor.getInstance(PluginManager.java:1258) at hudson.maven.PluginImpl.init(PluginImpl.java:58) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:106) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:176) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:905) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Oct 09, 2015 8:00:04 PM hudson.ExtensionFinder$Sezpoz _find WARNING: Failed to load hudson.ExtensionFinder$GuiceFinder java.lang.InstantiationException: com.google.inject.CreationException: Guice creation errors: 1) Could not find a suitable constructor in jenkins.model.Jenkins. Classes must have either one (and only one) constructor annotated with @Inject or a zero-argument constructor that is not private. at jenkins
[JIRA] [core] (JENKINS-28955) Jenkins unusable after downgrade from latest weekly release to LTS
Title: Message Title Oleg Nenashev commented on JENKINS-28955 Re: Jenkins unusable after downgrade from latest weekly release to LTS I see the same issue during plugins debug against 1.609.3 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-28955) Jenkins unusable after downgrade from latest weekly release to LTS
Title: Message Title Kanstantsin Shautsou edited a comment on JENKINS-28955 Re: Jenkins unusable after downgrade from latest weekly release to LTS Got the same issue after disabling/uninstalling number of plugins on 1.609.3 {code}hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.WebAppMain$3.run(WebAppMain.java:237)Caused by: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:44) at jenkins.model.Jenkins.executeReactor(Jenkins.java:915) at jenkins.model.Jenkins.(Jenkins.java:814) at hudson.model.Hudson.(Hudson.java:83) at hudson.model.Hudson.(Hudson.java:79) at hudson.WebAppMain$3.run(WebAppMain.java:225)Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:176) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:904) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:106) ... 8 moreCaused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:653) at java.util.ArrayList.get(ArrayList.java:429) at hudson.ExtensionList.get(ExtensionList.java:158) at hudson.PluginManager$PluginUpdateMonitor.getInstance(PluginManager.java:1257) at hudson.maven.PluginImpl.init(PluginImpl.java:58) ... 13 more{code} Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-28955) Jenkins unusable after downgrade from latest weekly release to LTS
Title: Message Title Kanstantsin Shautsou reopened an issue Jenkins / JENKINS-28955 Jenkins unusable after downgrade from latest weekly release to LTS Change By: Kanstantsin Shautsou Resolution: Cannot Reproduce Status: Closed Reopened 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-28955) Jenkins unusable after downgrade from latest weekly release to LTS
Title: Message Title Kanstantsin Shautsou commented on JENKINS-28955 Re: Jenkins unusable after downgrade from latest weekly release to LTS Got the same issue after disabling/uninstalling number of plugins on 1.609.3 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-28955) Jenkins unusable after downgrade from latest weekly release to LTS
Title: Message Title Shannon Kerr closed an issue as Cannot Reproduce Jenkins / JENKINS-28955 Jenkins unusable after downgrade from latest weekly release to LTS Change By: Shannon Kerr Status: Resolved Closed 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-28955) Jenkins unusable after downgrade from latest weekly release to LTS
Title: Message Title Shannon Kerr resolved as Cannot Reproduce Jenkins / JENKINS-28955 Jenkins unusable after downgrade from latest weekly release to LTS Change By: Shannon Kerr Status: Open Resolved Resolution: Cannot Reproduce 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-28955) Jenkins unusable after downgrade from latest weekly release to LTS
Title: Message Title Shannon Kerr commented on JENKINS-28955 Re: Jenkins unusable after downgrade from latest weekly release to LTS Sorry, I had to move on. I created a new sandbox from a backup of our official env and pulled over my jobs. 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-28955) Jenkins unusable after downgrade from latest weekly release to LTS
Title: Message Title Daniel Beck commented on JENKINS-28955 Re: Jenkins unusable after downgrade from latest weekly release to LTS Did you try to clear out the war directory? /var/cache/jenkins or something like that? 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-28955) Jenkins unusable after downgrade from latest weekly release to LTS
Title: Message Title Shannon Kerr updated an issue Jenkins / JENKINS-28955 Jenkins unusable after downgrade from latest weekly release to LTS Change By: Shannon Kerr After doing a dpkg -i of jenkins_1.609.1_all.deb on top of my current weekly release of jenkins_1. 609 617_all . 1_all. deb, Jenkins is no longer usable (see main screen screenshot).I tried going back to 617, but I get the same result. This is my Jenkins sandbox. I'm not sure what to do to recover from this. I was going to test the latest LTS so we could move our production Jenkins instance to it, but my sandbox is unusable now, so we're stuck unless I copy over a new Jenkins backup and set it back up as a sandbox. I'm not sure that solves my problem though. I've switched around between Jenkins releases before and never had this happen.Ouptut:{quote}hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.WebAppMain$3.run(WebAppMain.java:237)Caused by: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:44) at jenkins.model.Jenkins.executeReactor(Jenkins.java:915) at jenkins.model.Jenkins.(Jenkins.java:814) at hudson.model.Hudson.(Hudson.java:83) at hudson.model.Hudson.(Hudson.java:79) at hudson.WebAppMain$3.run(WebAppMain.java:225)Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:176) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:904) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) 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)Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:106) ... 8 moreCaused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:635) at java.util.ArrayList.get(ArrayList.java:411) at hudson.ExtensionList.get(ExtensionList.java:158) at hudson.PluginManager$PluginUpdateMonitor.getInstance(PluginManager.java:1257) at hudson.maven.PluginImpl.init(PluginImpl.java:58) ... 13 more{quote}
[JIRA] [core] (JENKINS-28955) Jenkins unusable after downgrade from latest weekly release to LTS
Title: Message Title Shannon Kerr edited a comment on JENKINS-28955 Re: Jenkins unusable after downgrade from latest weekly release to LTS Updated to latest weekly release and issue still exists. I disabled security on this instance, but that made no difference. I would hate will go to lose all of a non-sandbox backup and migrate my sandbox projects and configuration to the restored non-sandbox backup . I hope someone Not ideal, but will be able to give get me some guidance working again . 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-28955) Jenkins unusable after downgrade from latest weekly release to LTS
Title: Message Title Shannon Kerr commented on JENKINS-28955 Re: Jenkins unusable after downgrade from latest weekly release to LTS Updated to latest weekly release and issue still exists. I disabled security on this instance, but that made no difference. I would hate to lose all of my projects and configuration. I hope someone will be able to give me some guidance. 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-28955) Jenkins unusable after downgrade from latest weekly release to LTS
Title: Message Title Shannon Kerr created an issue Jenkins / JENKINS-28955 Jenkins unusable after downgrade from latest weekly release to LTS Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2015-06-17 at 3.05.06 PM.png Components: core Created: 17/Jun/15 7:12 PM Environment: Host: Ubuntu 14.04 server VM Jenkins 1.617 --> Jenkins 1.609.1 Priority: Major Reporter: Shannon Kerr After doing a dpkg -i of jenkins_1.609.1_all.deb on top of my current weekly release of jenkins_1.609.1_all.deb, Jenkins is no longer usable (see main screen screenshot). I tried going back to 617, but I get the same result. This is my Jenkins sandbox. I'm not sure what to do to recover from this. I was going to test the latest LTS so we could move our production Jenkins instance to it, but my sandbox is unusable now, so we're stuck unless I copy over a new Jenkins backup and set it back up as a sandbox. I'm not sure that solves my problem though. I've switched around between Jenkins