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

Docs do not make it clear that string variables need double quotes

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • email-ext-plugin
    • None

      When using the ENV content, ${ENV,var="path"} works but ${ENV,var=path} does not. Improve documentation so that it's clear that quotes are required.

          [JENKINS-5322] Docs do not make it clear that string variables need double quotes

          ashlux added a comment -

          These comments suggests that this actually works. Perhaps I'm just doing something wrong or misunderstand the functionality. Either way, I'll figure it out and fix it if I find a problem.

          ashlux added a comment - These comments suggests that this actually works. Perhaps I'm just doing something wrong or misunderstand the functionality. Either way, I'll figure it out and fix it if I find a problem.

          SCM/JIRA link daemon added a comment -

          Code changed in hudson
          User: : ashlux
          Path:
          trunk/hudson/plugins/email-ext/src/main/java/hudson/plugins/emailext/EmailExtHelp.java
          http://jenkins-ci.org/commit/26331
          Log:
          [FIXED JENKINS-5322] Add to docs about string variables needing a double quote as a delimiter.

          SCM/JIRA link daemon added a comment - Code changed in hudson User: : ashlux Path: trunk/hudson/plugins/email-ext/src/main/java/hudson/plugins/emailext/EmailExtHelp.java http://jenkins-ci.org/commit/26331 Log: [FIXED JENKINS-5322] Add to docs about string variables needing a double quote as a delimiter.

          Rakesh Nambiar added a comment -

          Not worked in the below scenario.

          I have a string parameter called:

                    SERVERNAME

          Override this value through one of my build steps:

          XX="MY_SERVER"  

          SERVERNAME=$XX 

           

          In the extended email I have tried the below :

          $SERVERNAME [Not worked]

          ${SERVERNAME} [Not worked]

          $

          {ENV,var=SERVERNAME} [Not worked]

          Rakesh Nambiar added a comment - Not worked in the below scenario. I have a string parameter called:           SERVERNAME Override this value through one of my build steps: XX="MY_SERVER"   SERVERNAME=$XX    In the extended email I have tried the below : $SERVERNAME [Not worked] ${SERVERNAME} [Not worked] $ {ENV,var=SERVERNAME} [Not worked]

            ashlux ashlux
            ashlux ashlux
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: