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

EnvInject claims global env vars are unresolved on slave

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Component/s: envinject-plugin
    • Labels:
      None
    • Environment:
      EnvInject 1.55
      Jenkins 1.472
    • Similar Issues:

      Description

      Steps to reproduce

      1. Go to Manage Jenkins > Configure System and check 'Environment variables' under 'Global properties'
      2. Add a variable called GLOBAL_VAR with the value $HOME/foo and save
      3. Create a new job, check 'Prepare an environment for the run' and put DERIVED_VAR=$GLOBAL_VAR/bar in 'Properties Content'.
      4. Check 'Restrict where this project can be run' and make it run on a node OTHER THAN master
      5. Add an 'Execute shell' build step and add:

      echo $GLOBAL_VAR
      echo $DERIVED_VAR

      6. Run job

      Expected output

      Building remotely on not_master in workspace /tmp/slave/workspace/env_test
      [env_test] $ /bin/sh -xe /var/folders/t5/2y9vs7rj20b7h_h3hj_d_ly98mbs7g/T/hudson2936884432042635298.sh
      /home/jenkins/foo
      /home/jenkins/foo/bar

      Actual output

      [EnvInject] - Unset unresolved 'GLOBAL_VAR' variable.
      [EnvInject] - Unset unresolved 'DERIVED_VAR' variable.
      Building remotely on not_master in workspace /tmp/slave/workspace/env_test
      [env_test] $ /bin/sh -xe /var/folders/t5/2y9vs7rj20b7h_h3hj_d_ly98mbs7g/T/hudson2936884432042635298.sh
      /home/jenkins/foo
      
      

        Attachments

          Activity

            People

            • Assignee:
              gbois Gregory Boissinot
              Reporter:
              jorgenpt Jørgen Tjernø
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: