broke on 2.0 upgrade

[Josh Santangelo]

I was able to install 2.0, then clicked the button to "install new features". That went ok, and Jenkins starts, but it shows an error on the main page. Attached is a much more verbose log file.

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:1020)
	at jenkins.model.Jenkins.<init>(Jenkins.java:864)
	at hudson.model.Hudson.<init>(Hudson.java:85)
	at hudson.model.Hudson.<init>(Hudson.java:81)
	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:175)
	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
	at jenkins.model.Jenkins$8.runTask(Jenkins.java:1009)
	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(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104)
	... 8 more
Caused by: java.lang.NullPointerException
	at hudson.plugins.git.GitSCM.onLoaded(GitSCM.java:1734)
	... 13 more

[Daniel Beck]

> On 26.04.2016, at 20:35, Josh Santangelo <jo...@stimulant.com> wrote:
>
> I was able to install 2.0, then clicked the button to "install new features". That went ok, and Jenkins starts, but it shows an error on the main page. Attached is a much more verbose log file.

Are there no other errors in the Jenkins log?

[Daniel Beck]

Nevermind, found it.

> Apr 26, 2016 11:30:39 AM hudson.ClassicPluginStrategy createPluginWrapper
> INFO: Plugin ant.jpi is disabled
> Apr 26, 2016 11:30:39 AM hudson.ClassicPluginStrategy createPluginWrapper
> INFO: Plugin copyartifact.jpi is disabled
> Apr 26, 2016 11:30:39 AM hudson.ClassicPluginStrategy createPluginWrapper
> INFO: Plugin cvs.jpi is disabled
> Apr 26, 2016 11:30:39 AM hudson.ClassicPluginStrategy createPluginWrapper
> INFO: Plugin external-monitor-job.jpi is disabled
> Apr 26, 2016 11:30:40 AM hudson.ClassicPluginStrategy createPluginWrapper
> INFO: Plugin github-api.jpi is disabled
> Apr 26, 2016 11:30:41 AM hudson.ClassicPluginStrategy createPluginWrapper
> INFO: Plugin github.jpi is disabled
> Apr 26, 2016 11:30:41 AM hudson.ClassicPluginStrategy createPluginWrapper
> INFO: Plugin javadoc.jpi is disabled
> Apr 26, 2016 11:30:41 AM hudson.ClassicPluginStrategy createPluginWrapper
> INFO: Plugin pam-auth.jpi is disabled
> Apr 26, 2016 11:30:41 AM hudson.ClassicPluginStrategy createPluginWrapper
> INFO: Plugin shelve-project-plugin.jpi is disabled
> Apr 26, 2016 11:30:42 AM hudson.ClassicPluginStrategy createPluginWrapper
> INFO: Plugin ssh-slaves.jpi is disabled
> Apr 26, 2016 11:30:42 AM hudson.ClassicPluginStrategy createPluginWrapper
> INFO: Plugin subversion.jpi is disabled
> Apr 26, 2016 11:30:42 AM hudson.ClassicPluginStrategy createPluginWrapper
> INFO: Plugin translation.jpi is disabled

Enable some or all of these plugins and restart. Probably an unsatisfied dependency (Jenkins is kind of weird when it comes to plugin dependencies, changes are coming soon).

[Josh Santangelo]

Thanks for the reply -- what's the best way to do that if I'm unable to get to the GUI?

[Daniel Beck]

> On 26.04.2016, at 21:01, Josh Santangelo <jo...@stimulant.com> wrote:
>
> Thanks for the reply -- what's the best way to do that if I'm unable to get to the GUI?

Delete JENKINS_HOME/plugins/pluginname.jpi.disabled for the respective plugins.

[Josh Santangelo]

I think that fixed it. Thanks again.

[Paulo Moreira]

+1 fixed thanks :)

cd /var/lib/jenkins/plugins

ls -la | grep disable

if files rm

Did the trick!

[Daniel Beck]

> On 04.05.2016, at 12:48, Paulo Moreira <pmes...@gmail.com> wrote:
>
> +1 fixed thanks :)
>
> cd /var/lib/jenkins/plugins
> ls -la | grep disable
>
> if files rm
>
> Did the trick!

FWIW we included a change in 2.1 that results in new plugin installations no longer causing this problem: Disabled dependencies are now automatically enabled, similar to how dependencies that aren't installed get installed.

So unless you mess around with the plugins/ directory directly, admins should be protected from this situation for any plugin installation.