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

The NodeJS plugin breaks the Xvnc plugin

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: nodejs-plugin, xvnc-plugin
    • Labels:
      None
    • Environment:
      NodeJS plugin v0.2.1 (latest) and Xvnc plugin 1.21 (latest) on Jenkins v1.596.3 (LTS), Ubuntu 14.10 with vnc4server v4.1.1+xorg4.3.0-37ubuntu5.2
    • Similar Issues:

      Description

      Enabling the NodeJS plugin on a job that has the Xvnc plugin enabled results in a broken Xvnc plugin. The following log is from such a build:

      ...
      Starting xvnc
      [TEST-nodejs-xvnc] $ /usr/bin/vncserver :76 -geometry 1920x1280
      /usr/bin/env: perl: No such file or directory
      Starting xvnc
      [TEST-nodejs-xvnc] $ /usr/bin/vncserver :46 -geometry 1920x1280
      /usr/bin/env: perl: No such file or directory
      Starting xvnc
      ...
      FATAL: Failed to run '/usr/bin/vncserver :22 -geometry 1920x1280' (exit code 127), blacklisting display #22; consider checking the "Clean up before start" option
      java.io.IOException: Failed to run '/usr/bin/vncserver :22 -geometry 1920x1280' (exit code 127), blacklisting display #22; consider checking the "Clean up before start" option
          at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:119)
          at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)
          at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)
          at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)
          at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)
          at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)
          at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)
          at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)
          at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)
          at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)
          at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:116)
          at hudson.plugins.xvnc.Xvnc.setUp(Xvnc.java:79)
          at hudson.model.Build$BuildExecution.doRun(Build.java:154)
          at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533)
          at hudson.model.Run.execute(Run.java:1758)
          at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
          at hudson.model.ResourceController.execute(ResourceController.java:89)
          at hudson.model.Executor.run(Executor.java:240)
      

      At first I thought that this was a PATH issue, but the Xvnc plugin works if I disable the NodeJS plugin and use the EnvInject plugin to set the PATH to what the NodeJS plugin would set it to.

        Attachments

          Activity

          Hide
          davidparsson David Pärsson added a comment - - edited

          The custom-tools plugin seems to have had, and resolved, the exact same problem in JENKINS-20560.

          Show
          davidparsson David Pärsson added a comment - - edited The custom-tools plugin seems to have had, and resolved, the exact same problem in JENKINS-20560 .
          Hide
          davidparsson David Pärsson added a comment - - edited

          When modifying the Xvnc Command line, in Jenkins' system configuration, to be echo $PATH I get this result:

          [TEST-nodejs-xvnc] $ echo ${PATH}
          /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.38/bin:null
          
          Show
          davidparsson David Pärsson added a comment - - edited When modifying the Xvnc Command line, in Jenkins' system configuration, to be echo $PATH I get this result: [TEST-nodejs-xvnc] $ echo ${PATH} / var /lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.38/bin: null
          Hide
          vkarhaltsev Slava Karhaltsev added a comment -

          as a workaround you can configure Xvnc Comman Line to be like this:

          /bin/sh -c "PATH=/bin:/usr/bin:/usr/local/bin:$PATH /usr/bin/vncserver :$DISPLAY_NUMBER -geometry 1920x1080"
          
          Show
          vkarhaltsev Slava Karhaltsev added a comment - as a workaround you can configure Xvnc Comman Line to be like this: /bin/sh -c "PATH=/bin:/usr/bin:/usr/local/bin:$PATH /usr/bin/vncserver :$DISPLAY_NUMBER -geometry 1920x1080"
          Hide
          nfalco Nikolas Falco added a comment -

          Fixed in 1.0.x

          This issue is similar to JENKINS-28578

          Show
          nfalco Nikolas Falco added a comment - Fixed in 1.0.x This issue is similar to JENKINS-28578

            People

            • Assignee:
              Unassigned
              Reporter:
              davidparsson David Pärsson
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: