Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Not a Bug
    • Affects Version/s: 2.1.8, 2.2.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      Description

      When trying to launch a job in a slave node, the plugin fails with the following error:

      ERROR: Failed to parse POMs
      java.io.IOException: Cannot run program "java" (in directory "/development/application/build-data/jenkins/workspace"): java.io.IOException: error=2, No such file or directory
      at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)
      at hudson.Proc$LocalProc.<init>(Proc.java:244)
      at hudson.Proc$LocalProc.<init>(Proc.java:216)
      at hudson.Launcher$LocalLauncher.launch(Launcher.java:773)
      at hudson.Launcher$ProcStarter.start(Launcher.java:353)
      at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:998)
      at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:965)
      at hudson.remoting.UserRequest.perform(UserRequest.java:118)
      at hudson.remoting.UserRequest.perform(UserRequest.java:48)
      at hudson.remoting.Request$2.run(Request.java:326)
      at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      at java.util.concurrent.FutureTask.run(FutureTask.java:138)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      at java.lang.Thread.run(Thread.java:662)
      Caused by: java.io.IOException: java.io.IOException: error=2, No such file or directory
      at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
      at java.lang.ProcessImpl.start(ProcessImpl.java:65)
      at java.lang.ProcessBuilder.start(ProcessBuilder.java:453)

      Additional or probably revelant information:

      • Trying to inject environment variables with the EnvInject plugin causes no effect on the path resolution.
      • Command line without the Artifactory plugin off:

      /tools/jdk/jdk1.6.0_34/bin/java -cp /development/application/build-data/jenkins/maven3-agent.jar:/home/webadmin/tools/apache-maven/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /home/webadmin/tools/apache-maven /development2/application/build-data/jenkins/slave.jar /development/application/build-data/jenkins/maven3-interceptor.jar /development/application/build-data/jenkins/maven3-interceptor-commons.jar 44525

      • Command line, that fails, with the Artifactory plugin on:

      java -Dm3plugin.lib=/development/application/build-data/jenkins/cache/artifactory-plugin/2.1.8 -Dmaven3.interceptor.common=/development2/application/build-data/jenkins/cache/artifactory-plugin/2.1.8 -cp /development2/application/build-data/jenkins/maven3-agent.jar:/home/webadmin/tools/apache-maven/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /home/webadmin/tools/apache-maven /development/application/build-data/jenkins/slave.jar /development/application/build-data/jenkins/maven3-interceptor.jar /development/application/build-data/jenkins/maven3-interceptor-commons.jar 45639

        Attachments

          Activity

            People

            • Assignee:
              yossis Yossi Shaul
              Reporter:
              otavio021 Otavio R. Piske
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: