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

Environment variables from setenv plugin are not inherited/parsed by batch tasks

    Details

    • Type: Bug
    • Status: Reopened
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: batch-task-plugin
    • Labels:
      None
    • Environment:
      Hudson 1.344, Hudson batch task plugin 1.12
    • Similar Issues:

      Description

      Some last Hudson version brought a new "Set environment variables" field in job configuration.
      This environment variables not inherited or parsed by shell tasks.

      One has to duplicate the needed variables in order to be used in task's script commands.

      Although the job's environment variables are passed, I've only tested these: parameter variables, $WORKSPACE, $JAVA_HOME, $CLEARCASE_VIEWNAME, etc. Global Environment variables set in hudson's configuration are also correctly parsed.

      I don't know if this an issue with tasks or because the "Set environment variables" field is coming after tasks definition in job's configuration view.

      Thanks in advance.


      UPDATED!

        Attachments

          Activity

            People

            • Assignee:
              abayer Andrew Bayer
              Reporter:
              hmonteiro hmonteiro
            • Votes:
              2 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: