Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: git-plugin
    • Labels:
      None
    • Environment:
      Ubuntu Server 64 bits
    • Similar Issues:

      Description

      Hi,

      I was updating my plugins then after update I can't access anymore my jenkins. I get the following error:

      [!] Erro

      org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException
      at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246)
      at jenkins.InitReactorRunner.run(InitReactorRunner.java:43)
      at jenkins.model.Jenkins.executeReactor(Jenkins.java:849)
      at jenkins.model.Jenkins.<init>(Jenkins.java:761)
      at hudson.model.Hudson.<init>(Hudson.java:81)
      at hudson.model.Hudson.<init>(Hudson.java:77)
      at hudson.WebAppMain$2.run(WebAppMain.java:217)
      Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException
      at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124)
      at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184)
      at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
      at jenkins.model.Jenkins$6.runTask(Jenkins.java:838)
      at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
      at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
      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)
      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:616)
      at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120)
      ... 8 more
      Caused by: java.lang.NullPointerException
      at hudson.plugins.git.GitTool.onLoaded(GitTool.java:74)
      ... 13 more

        Attachments

          Issue Links

            Activity

            Hide
            redlab Balder VC added a comment -

            Updating git.jpi to version 2.0 seemed to fix it on our instance.

            Show
            redlab Balder VC added a comment - Updating git.jpi to version 2.0 seemed to fix it on our instance.
            Hide
            redlab Balder VC added a comment -

            It returns when restarting jenkins. But installing the plugin does not give issues.

            Show
            redlab Balder VC added a comment - It returns when restarting jenkins. But installing the plugin does not give issues.
            Hide
            markewaite Mark Waite added a comment -

            I was able to see a similar null pointer exception if I disabled the credentials plugin while the git plugin and the git client plugin were both enabled. When I restarted Jenkins, it failed to restart with the null pointer exception.

            After doing that, I removed plugins/credentials.jpi.disabled and restarted Jenkins. It started correctly. The credentials plugin must be enabled for the git plugin or the git client plugin (or both).

            There may need to be some core extension which will allow a plugin to explicitly declare that it depends on another plugin being enabled.

            Show
            markewaite Mark Waite added a comment - I was able to see a similar null pointer exception if I disabled the credentials plugin while the git plugin and the git client plugin were both enabled. When I restarted Jenkins, it failed to restart with the null pointer exception. After doing that, I removed plugins/credentials.jpi.disabled and restarted Jenkins. It started correctly. The credentials plugin must be enabled for the git plugin or the git client plugin (or both). There may need to be some core extension which will allow a plugin to explicitly declare that it depends on another plugin being enabled.
            Hide
            axeluhl Axel Uhl added a comment -

            Thanks, Mark. I started over with a fresh Jenkins under Ubuntu, upgraded the .war file to the latest release (1.532.2 as of this writing) and installed the credentials plugin. Of course, I had to use the JGit implementation instead of an external git executable to get the benefits of the credentials plugin, but then, fetching from git worked like a charm.

            Show
            axeluhl Axel Uhl added a comment - Thanks, Mark. I started over with a fresh Jenkins under Ubuntu, upgraded the .war file to the latest release (1.532.2 as of this writing) and installed the credentials plugin. Of course, I had to use the JGit implementation instead of an external git executable to get the benefits of the credentials plugin, but then, fetching from git worked like a charm.
            Hide
            markewaite Mark Waite added a comment -

            I'm glad you were able to authenticate. The external git executable should also work with the credentials plugin.

            Show
            markewaite Mark Waite added a comment - I'm glad you were able to authenticate. The external git executable should also work with the credentials plugin.

              People

              • Assignee:
                ndeloof Nicolas De Loof
                Reporter:
                dextervip Rafael Tavares
              • Votes:
                5 Vote for this issue
                Watchers:
                14 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: