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

XShell not truly using PATH variable to execute stuff

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: xshell-plugin
    • Labels:
      None
    • Environment:
      Fedora 16, running Java: OpenJDK Runtime Environment (IcedTea6 1.11.6) (fedora-71.1.11.6.fc16-x86_64)
      OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
    • Similar Issues:

      Description

      I've found that I cannot run a script defined to the PATH environment variable. For the given slave-node, we set PATH in the slave-node configuration. We have a specific script (qt48-run) which is a wrapper-script, to add certain elements to the PATH and LD_LIBRARY_PATH. The wrapper-script resides in a directory we define to the slave-node-PATH. We cannot run that wrapper script.

      To illustrate, we made a job that just runs "printenv PATH"

      Execute Shell: printenv PATH
      Execute Shell: qt48-run printenv PATH
      Execute Shell: echo -------------------------------
      Invoke XShell command: printenv PATH
      Invoke XShell command: qt48-run printenv PATH

      The resulting console output (with stack-trace) is attached. The xshell plugin just simply does not find the specific "qt48-run" wrapper script. In our case, that script resides at /usr/devtools/linux-environments/.

      ... by the way, the xshell documentation does say that a script can be run from the PATH, and not necessarily in the local directory.

        Attachments

          Activity

          Hide
          macetw macetw added a comment -

          A small clarification point: the given node we are using is not a slave node. Our bug is happening with defining the PATH on the "master" node, and the script is happening on the master.

          Note that the "Execute Shell" command of "qt48-run printenv..." works fine, as intended, with adding qt-bin to the PATH. But the corresponding XShell call does not.

          Show
          macetw macetw added a comment - A small clarification point: the given node we are using is not a slave node. Our bug is happening with defining the PATH on the "master" node, and the script is happening on the master. Note that the "Execute Shell" command of "qt48-run printenv..." works fine, as intended, with adding qt-bin to the PATH. But the corresponding XShell call does not.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            macetw macetw
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: