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

User Hudson Global environment variables not set with m2-extra-steps for Shell extra step

    XMLWordPrintable

Details

    Description

      I have a specific Global environment variables set in Hudson/Manage
      Hudson/Configure System/Global Properties, called TEST.

      When I use a 'Free style' Hudson job with a Shell script, I can use ${TEST} in my
      shell command.

      When it is defined in a m2 extra step, Shell script does not see the TEST variable
      (I did a set command on both case), whereas for ANT m2 extra step, ANT script see
      it.

      Attachments

        Issue Links

          is duplicated by

          Patch - JENKINS-4851 Taking into account global properties

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            abrugger abrugger created issue -
            abayer Andrew Bayer made changes -
            Field Original Value New Value
            Link This issue is duplicated by JENKINS-4851 [ JENKINS-4851 ]
            scm_issue_link SCM/JIRA link daemon made changes -
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Resolved [ 5 ]
            abayer Andrew Bayer made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 134774 ] JNJira + In-Review [ 203053 ]

            People

              abayer Andrew Bayer
              abrugger abrugger
              Votes:
              2 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: