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

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

    Details

    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            ashlux ashlux created issue -
            Hide
            ashlux 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.

            Show
            ashlux 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 ashlux made changes -
            Field Original Value New Value
            Link This issue duplicates JENKINS-2413 [ JENKINS-2413 ]
            ashlux ashlux made changes -
            Summary email-ext $ENV variable doesn't work String varibles shouldn't require quotes
            Description When using the ENV content, ${ENV} works fine but ${ENV, var="somevar"} does not work. More info: http://n4.nabble.com/How-to-use-environment-variables-td1012822.html When using the ENV content, ${ENV,var="path"} works but ${ENV,var=path}. Both should be supported.
            ashlux ashlux made changes -
            Description When using the ENV content, ${ENV,var="path"} works but ${ENV,var=path}. Both should be supported. When using the ENV content, ${ENV,var="path"} works but ${ENV,var=path} does not.
            ashlux ashlux made changes -
            Description When using the ENV content, ${ENV,var="path"} works but ${ENV,var=path} does not. 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.
            ashlux ashlux made changes -
            Summary String varibles shouldn't require quotes Docs do not make it clear that string variables need double quotes
            Issue Type Bug [ 1 ] Improvement [ 4 ]
            Priority Major [ 3 ] Minor [ 4 ]
            ashlux ashlux made changes -
            Status Open [ 1 ] Closed [ 6 ]
            Resolution Fixed [ 1 ]
            Hide
            scm_issue_link 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.

            Show
            scm_issue_link 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.
            rajpra rajpra made changes -
            Link This issue is duplicated by JENKINS-3605 [ JENKINS-3605 ]
            mdonohue mdonohue made changes -
            Link This issue is duplicated by JENKINS-3605 [ JENKINS-3605 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 135411 ] JNJira + In-Review [ 203465 ]
            Hide
            rakeshnambiar 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]

            Show
            rakeshnambiar 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]

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: