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

Fatal error when you use a slave and try to launch command which need to be in the path after build (after "channel stopped").

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • maven-plugin
    • None

      Fatal error when you use a slave and try to launch command which need to be in the path after build (after "channel stopped").

      When you see "channel stopped" (after a build), all the variables like path are anymore not setted.
      So all commands (like mvn or others) will not work.

      In my case, reports or maven extras step does not work in slave.

      This is an example of the problem.
      In build, I do mvn clean install (and it works).
      After I use a maven extra step after and maven or any command in path does not work.

      I hope I'm clear. It is very blocking issue.

      Log file.

      [INFO] ------------------------------------------------------------------------
      [INFO] BUILD SUCCESSFUL
      [INFO] ------------------------------------------------------------------------
      [INFO] Total time: 6 minutes 8 seconds
      [INFO] Finished at: Mon Jun 07 20:53:10 CEST 2010
      [INFO] Final Memory: 99M/208M
      [INFO] ------------------------------------------------------------------------
      channel stopped
      [trunk] $ mvn -fn -P javadoc,test,testcampain,taglist,changes,overview,sonar,umlGraph,versions -Djava.awt.headless=true sonar:sonar site:site site-deploy
      FATAL: command execution failed
      java.io.IOException: Cannot run program "mvn" (in directory "/home/frtdevxpp/hudson/jobs/workspace/ARC-CTT-Nightly-Integration/trunk"): java.io.IOException: error=2, No such file or directory
      at java.lang.ProcessBuilder.start(ProcessBuilder.java:459)
      at hudson.Proc$LocalProc.<init>(Proc.java:149)
      at hudson.Proc$LocalProc.<init>(Proc.java:121)
      at hudson.Launcher$LocalLauncher.launch(Launcher.java:636)
      at hudson.Launcher$ProcStarter.start(Launcher.java:271)
      at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:783)
      at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:757)
      at hudson.remoting.UserRequest.perform(UserRequest.java:114)
      at hudson.remoting.UserRequest.perform(UserRequest.java:48)
      at hudson.remoting.Request$2.run(Request.java:270)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
      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:619)
      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:452)
      ... 15 more

          [JENKINS-6718] Fatal error when you use a slave and try to launch command which need to be in the path after build (after "channel stopped").

          Hi,

          I've exactly the same problem.
          Jenkins : 1.500
          Sonar Plugin : 2.0.1

          Do you have found a workaround for this issue ?

          Michael Pailloncy added a comment - Hi, I've exactly the same problem. Jenkins : 1.500 Sonar Plugin : 2.0.1 Do you have found a workaround for this issue ?

          Not a slave issue. The Maven project type should be setting the path to include maven from the very start of the job not just for the maven steps. The user is only not seeing this issue on master because their path likely has maven on it anyway

          Stephen Connolly added a comment - Not a slave issue. The Maven project type should be setting the path to include maven from the very start of the job not just for the maven steps. The user is only not seeing this issue on master because their path likely has maven on it anyway

          Explicitly selecting the maven version on post build step instead of "standard", solves the problem.

          Oliver Thomsen added a comment - Explicitly selecting the maven version on post build step instead of "standard", solves the problem.

            kohsuke Kohsuke Kawaguchi
            alexandre_navarro alexandre_navarro
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: