-
Improvement
-
Resolution: Fixed
-
Minor
-
Jenkins version 2.235.1
Email Extension Plugin version 2.69
Token Macro Plugin version 2.12
-
-
270.v8c2ce50dc4fc
It seems as if environmental variables don't work with the emailext plugin. I am using declarative pipelines, but regardless of what I try the ${ENV, var=""} returns nothing. I can see that the double quoted subject "$VERSION" is correctly replaced and other tokens work such as single quoted '${BUILD_STATUS}' work, but '${ENV, var=""}' and '${ENV, var="VERSION"}' are always replaced empty. Same occurs with variables such as $PATH.
pipeline {
environment {
VERSION = "1.0.0"
}
// ...
// stages
// ...
post {
always {
emailext (
to: 'DEFAULT_RECIPIENTS',
subject: "$VERSION",
body: '${ENV, var="VERSION"}'
)
}
}
}
Regards
Erik Hughes
[JENKINS-63551] Environmental variables are always empty in email-ext plugin
| Description |
Original:
It seems as if environmental variables don't work with the emailext plugin. I am using declarative pipelines, but regardless of what I try the ${ENV, var=""} returns nothing. I can see that the double quoted subject $VERSION is correctly replaced and other tokens work such as '${BUILD_STATUS}' work, but never '${ENV, var=""}'. {code:java} pipeline { environment { VERSION = "1.0.0" } // ... // stages // ... post { always { emailext ( to: 'DEFAULT_RECIPIENTS', subject: "$VERSION", body: '${ENV, var="VERSION"}' ) } } } {code} Regards Erik Hughes |
New:
It seems as if environmental variables don't work with the emailext plugin. I am using declarative pipelines, but regardless of what I try the ${ENV, var=""} returns nothing. I can see that the double quoted subject $VERSION is correctly replaced and other tokens work such as '${BUILD_STATUS}' work, but never '${ENV, var=""}'. {code:java} pipeline { environment { VERSION = "1.0.0" } // ... // stages // ... post { always { emailext ( to: 'DEFAULT_RECIPIENTS', subject: "$VERSION", body: '${ENV, var="VERSION"}' ) } } } {code} Regards Erik Hughes |
| Description |
Original:
It seems as if environmental variables don't work with the emailext plugin. I am using declarative pipelines, but regardless of what I try the ${ENV, var=""} returns nothing. I can see that the double quoted subject $VERSION is correctly replaced and other tokens work such as '${BUILD_STATUS}' work, but never '${ENV, var=""}'. {code:java} pipeline { environment { VERSION = "1.0.0" } // ... // stages // ... post { always { emailext ( to: 'DEFAULT_RECIPIENTS', subject: "$VERSION", body: '${ENV, var="VERSION"}' ) } } } {code} Regards Erik Hughes |
New:
It seems as if environmental variables don't work with the emailext plugin. I am using declarative pipelines, but regardless of what I try the ${ENV, var=""} returns nothing. I can see that the double quoted subject "$VERSION" is correctly replaced and other tokens work such as single quoted '${BUILD_STATUS}' work, but never '${ENV, var=""}'. {code:java} pipeline { environment { VERSION = "1.0.0" } // ... // stages // ... post { always { emailext ( to: 'DEFAULT_RECIPIENTS', subject: "$VERSION", body: '${ENV, var="VERSION"}' ) } } } {code} Regards Erik Hughes |
| Description |
Original:
It seems as if environmental variables don't work with the emailext plugin. I am using declarative pipelines, but regardless of what I try the ${ENV, var=""} returns nothing. I can see that the double quoted subject "$VERSION" is correctly replaced and other tokens work such as single quoted '${BUILD_STATUS}' work, but never '${ENV, var=""}'. {code:java} pipeline { environment { VERSION = "1.0.0" } // ... // stages // ... post { always { emailext ( to: 'DEFAULT_RECIPIENTS', subject: "$VERSION", body: '${ENV, var="VERSION"}' ) } } } {code} Regards Erik Hughes |
New:
It seems as if environmental variables don't work with the emailext plugin. I am using declarative pipelines, but regardless of what I try the ${ENV, var=""} returns nothing. I can see that the double quoted subject "$VERSION" is correctly replaced and other tokens work such as single quoted '${BUILD_STATUS}' work, but '${ENV, var=""}' and '${ENV, var="VERSION"}' are always replaced empty. {code:java} pipeline { environment { VERSION = "1.0.0" } // ... // stages // ... post { always { emailext ( to: 'DEFAULT_RECIPIENTS', subject: "$VERSION", body: '${ENV, var="VERSION"}' ) } } } {code} Regards Erik Hughes |
| Description |
Original:
It seems as if environmental variables don't work with the emailext plugin. I am using declarative pipelines, but regardless of what I try the ${ENV, var=""} returns nothing. I can see that the double quoted subject "$VERSION" is correctly replaced and other tokens work such as single quoted '${BUILD_STATUS}' work, but '${ENV, var=""}' and '${ENV, var="VERSION"}' are always replaced empty. {code:java} pipeline { environment { VERSION = "1.0.0" } // ... // stages // ... post { always { emailext ( to: 'DEFAULT_RECIPIENTS', subject: "$VERSION", body: '${ENV, var="VERSION"}' ) } } } {code} Regards Erik Hughes |
New:
It seems as if environmental variables don't work with the emailext plugin. I am using declarative pipelines, but regardless of what I try the ${ENV, var=""} returns nothing. I can see that the double quoted subject "$VERSION" is correctly replaced and other tokens work such as single quoted '${BUILD_STATUS}' work, but '${ENV, var=""}' and '${ENV, var="VERSION"}' are always replaced empty. Same occurs with variables such as $PATH. {code:java} pipeline { environment { VERSION = "1.0.0" } // ... // stages // ... post { always { emailext ( to: 'DEFAULT_RECIPIENTS', subject: "$VERSION", body: '${ENV, var="VERSION"}' ) } } } {code} Regards Erik Hughes |
| Assignee | Original: Alex Earl [ slide_o_mix ] |
Basil Crow
made changes -
| Issue Type | Original: Bug [ 1 ] | New: Improvement [ 4 ] |
| Assignee | New: Alex Earl [ slide_o_mix ] |
| Released As | New: 270.v8c2ce50dc4fc | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Fixed but Unreleased [ 10203 ] |
| Status | Original: Fixed but Unreleased [ 10203 ] | New: Resolved [ 5 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |