Details
-
Type:
Improvement
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: email-ext-plugin
-
Labels:None
-
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
- duplicates
-
JENKINS-2413 [Email plugin] Read parameters/variables used during build
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue duplicates |
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. |
Summary | email-ext $ENV variable doesn't work | String varibles shouldn't require quotes |
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. |
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. |
Issue Type | Bug [ 1 ] | Improvement [ 4 ] |
Priority | Major [ 3 ] | Minor [ 4 ] |
Summary | String varibles shouldn't require quotes | Docs do not make it clear that string variables need double quotes |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Link |
This issue is duplicated by |
Link |
This issue is duplicated by |
Workflow | JNJira [ 135411 ] | JNJira + In-Review [ 203465 ] |