Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-63475

NoSuchMethodFound Exception while running the build

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

       

      When trying to build it in Jenkins  ->

      Executed kernel : PYTHON
      Language : PYTHON
      Platform : LINUX
      Type : TEXT
      Working directory : /var/lib/jenkins/workspace/GIT
      java.lang.NoSuchMethodError: org.apache.zeppelin.interpreter.util.ProcessLauncher.<init>(Lorg/apache/commons/exec/CommandLine;Ljava/util/Map;Ljava/lang/String;)V
      	at org.apache.zeppelin.jupyter.JupyterKernelInterpreter$JupyterKernelProcessLauncher.<init>(JupyterKernelInterpreter.java:313)
      	at org.apache.zeppelin.jupyter.JupyterKernelInterpreter.launchJupyterKernel(JupyterKernelInterpreter.java:191)
      	at org.apache.zeppelin.jupyter.JupyterKernelInterpreter.open(JupyterKernelInterpreter.java:121)
      	at org.apache.zeppelin.jupyter.JupyterInterpreter.internalInterpret(JupyterInterpreter.java:65)
      	at org.apache.zeppelin.interpreter.AbstractInterpreter.interpret(AbstractInterpreter.java:47)
      	at org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:110)
      	at io.jenkins.plugins.ml.IPythonKernelInterpreter.interpretCode(IPythonKernelInterpreter.java:86)
      	at io.jenkins.plugins.ml.IPythonInterpreterManager.invokeInterpreter(IPythonInterpreterManager.java:109)
      	at io.jenkins.plugins.ml.IPythonBuilder$ExecutorImpl.call(IPythonBuilder.java:327)
      	at io.jenkins.plugins.ml.IPythonBuilder$ExecutorImpl.call(IPythonBuilder.java:304)
      	at hudson.remoting.LocalChannel.call(LocalChannel.java:45)
      	at io.jenkins.plugins.ml.IPythonBuilder.perform(IPythonBuilder.java:130)
      	at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78)
      	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)
      	at hudson.model.Build$BuildExecution.build(Build.java:206)
      	at hudson.model.Build$BuildExecution.doRun(Build.java:163)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
      	at hudson.model.Run.execute(Run.java:1880)
      	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      	at hudson.model.ResourceController.execute(ResourceController.java:97)
      	at hudson.model.Executor.run(Executor.java:428)
      ERROR: org.apache.zeppelin.interpreter.util.ProcessLauncher.<init>(Lorg/apache/commons/exec/CommandLine;Ljava/util/Map;Ljava/lang/String;)V
      Finished: FAILURE
      
      

        Attachments

          Activity

          Hide
          loghijiaha Loghi Perinpanayagam added a comment -

          Fixed and Released v1.0..1

          Show
          loghijiaha Loghi Perinpanayagam added a comment - Fixed and Released v1.0..1
          Hide
          kinow Bruno P. Kinoshita added a comment -

          Loghi Perinpanayagam

          Sorry for this issue, I didn't think about testing that patch in a running instance to verify.

          I think Jenkins is simply looking at the dependencies first, and then our plugin classes. As it finds that class in the dependencies (Zeppelin JAR), it doesn't bother loading our special class.

          Loghi Perinpanayagam see: https://www.jenkins.io/doc/developer/plugin-development/dependencies-and-class-loading/#pluginfirstclassloader-and-its-discontents

          I think with that fix it should work. But testing it requires you to `mvn clean install`, then copy the `.hpi`, install a local Jenkins (e.g. download latest LTS version, then run something like `JENKINS_HOME=/tmp java -jar jenkins.war`) and install the plugin manually to verify it works.

          If so, then cut a new 1.0.1 I think. Let me know if that works.

          Bruno

          Show
          kinow Bruno P. Kinoshita added a comment - Loghi Perinpanayagam Sorry for this issue, I didn't think about testing that patch in a running instance to verify. I think Jenkins is simply looking at the dependencies first, and then our plugin classes. As it finds that class in the dependencies (Zeppelin JAR), it doesn't bother loading our special class. Loghi Perinpanayagam see: https://www.jenkins.io/doc/developer/plugin-development/dependencies-and-class-loading/#pluginfirstclassloader-and-its-discontents I think with that fix it should work. But testing it requires you to `mvn clean install`, then copy the `.hpi`, install a local Jenkins (e.g. download latest LTS version, then run something like `JENKINS_HOME=/tmp java -jar jenkins.war`) and install the plugin manually to verify it works. If so, then cut a new 1.0.1 I think. Let me know if that works. Bruno
          Hide
          loghijiaha Loghi Perinpanayagam added a comment - - edited

          Hi Bruno P. Kinoshita,

          This a blocker in the release. Our patched Zeppelin Launcher is not recognized while running the build.

          Show
          loghijiaha Loghi Perinpanayagam added a comment - - edited Hi Bruno P. Kinoshita , This a blocker in the release. Our patched Zeppelin Launcher is not recognized while running the build.

            People

            Assignee:
            loghijiaha Loghi Perinpanayagam
            Reporter:
            loghijiaha Loghi Perinpanayagam
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: