• Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • None
    • Jenkins Parameterized Trigger plugin ver. 2.7
      Jenkins ver. 1.397
      Ubuntu 10.04.1 LTS

      I have crated a new job and when using the parameterized trigger it is passing a literal '$VAR' instead of expanding $VAR.

      Here is some output from the job that is setting the variable (GIT_DESCRIBE):

      [workspace] $ /gsc/bin/bash -xe /tmp/hudson7947017773698263236.sh
      ++ git describe --tags
      + GIT_DESCRIBE=0.28-103-g0661244
      + export GIT_DESCRIBE
      + env
      + grep GIT_DESCRIBE
      GIT_DESCRIBE=0.28-103-g0661244
      Description set: 0.28-103-g0661244

      Using a predefined parameter I have "GIT_DESCRIBE=${GIT_DESCRIBE}" (without quotes) in the text field.

      Then the receiving job has the value of GIT_DESCRIBE as "${GIT_DESCRIBE}". If I start this job an enter a value for the GIT_DESCRIBE parameter as "0.28-103-g0661244" not only does it work but it also passes this value correctly onto the third/final job.

      P.S. I've never submitted a bug for Hudson/Jenkins before so please let me know if I am not doing this correctly.

          [JENKINS-8952] Not Expanding Environment Variable

          Nathan Nutter created issue -
          Nathan Nutter made changes -
          Description Original: I have crated a new job and when using the parameterized trigger it is passing a literal '$VAR' instead of expanding $VAR.

          Here is some output from the job that is setting the variable (GIT_DESCRIBE):
          bq. [workspace] $ /gsc/bin/bash -xe /tmp/hudson7947017773698263236.sh
          ++ git describe --tags
          + GIT_DESCRIBE=0.28-103-g0661244
          + export GIT_DESCRIBE
          + env
          + grep GIT_DESCRIBE
          GIT_DESCRIBE=0.28-103-g0661244
          Description set: 0.28-103-g0661244

          Using a predefined parameter I have "GIT_DESCRIBE=${GIT_DESCRIBE}" (without quotes) in the text field.

          Then the receiving job has the value of GIT_DESCRIBE as "${GIT_DESCRIBE}". If I start this job an enter a value for the GIT_DESCRIBE parameter as "0.28-103-g0661244" not only does it work but it also passes this value correctly onto the third/final job.

          P.S. I've never submitted a bug for Hudson/Jenkins before so please let me know if I am not doing this correctly.
          New: I have crated a new job and when using the parameterized trigger it is passing a literal '$VAR' instead of expanding $VAR.

          Here is some output from the job that is setting the variable (GIT_DESCRIBE):
          {quote}[workspace] $ /gsc/bin/bash -xe /tmp/hudson7947017773698263236.sh
          ++ git describe --tags
          + GIT_DESCRIBE=0.28-103-g0661244
          + export GIT_DESCRIBE
          + env
          + grep GIT_DESCRIBE
          GIT_DESCRIBE=0.28-103-g0661244
          Description set: 0.28-103-g0661244{quote}

          Using a predefined parameter I have "GIT_DESCRIBE=${GIT_DESCRIBE}" (without quotes) in the text field.

          Then the receiving job has the value of GIT_DESCRIBE as "${GIT_DESCRIBE}". If I start this job an enter a value for the GIT_DESCRIBE parameter as "0.28-103-g0661244" not only does it work but it also passes this value correctly onto the third/final job.

          P.S. I've never submitted a bug for Hudson/Jenkins before so please let me know if I am not doing this correctly.
          ikedam made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 139096 ] New: JNJira + In-Review [ 188332 ]

            huybrechts huybrechts
            nnutter Nathan Nutter
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: