[JIRA] (JENKINS-13277) Global environment variables are not being resolved in Email Notification Recipients list for maven 2/3 projects
Title: Message Title
Brent Duffy commented on JENKINS-13277
Re: Global environment variables are not being resolved in Email Notification Recipients list for maven 2/3 projects
We are seeing a similar issue with freestyle jobs on Jenkins 2.32.1. The problem we are seeing is that if an environment variable (or build parameter) isn't defined, the variable name is treated as a string literal instead of an empty string. We see this behavior in the "Recipients" field for the built-in "E-mail notification" post-build action as well as the "Project Recipient List" for the "Editable Email Notification" post-build action provided by the email-ext plugin. To replicate this issue, try to refer to an undefined environment variable in one of those fields. The environment variable syntax we're using in the recipient list is: emailaddress1 emailaddress2 $ {TEST_EMAIL_LIST} Basically, emails will always be delivered to emailaddress1 and emailaddress2, but some jobs need to supply additional email addresses via the TEST_EMAIL_LIST build parameter. We have a job that is a downstream to several other jobs. Some of the upstream jobs (but not all) supply TEST_EMAIL_LIST as a build parameter to the downstream job. When the variable is actually defined, everything works as expected, however when it is not defined, both the built-in "Email notification" and the "Editable Email Notification" plugin will try to send an email to the address "$TEST_EMAIL_LIST", which causes an error since it is not a valid address. We would expect that an undefined environment variable would be treated as an empty string, which is how they are treated in the bash shell.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-13277) Global environment variables are not being resolved in Email Notification Recipients list for maven 2/3 projects
[
https://issues.jenkins-ci.org/browse/JENKINS-13277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slide-O-Mix updated JENKINS-13277:
--
Component/s: (was: email-ext)
Global environment variables are not being resolved in Email Notification
Recipients list for maven 2/3 projects
Key: JENKINS-13277
URL: https://issues.jenkins-ci.org/browse/JENKINS-13277
Project: Jenkins
Issue Type: Bug
Components: notification
Affects Versions: current
Reporter: jfreej
When using a global environment variable, defined in Manage Jenkins
Configure System Environment Variables (e.g. ALERT_EMAIL_LIST), in the
Email Notification Recipients list of a maven 2/3 project (e.g.
${ALERT_EMAIL_LIST}) the environment variable is not resolved. In the
console output we see: Sending e-mails to: ${ALERT_EMAIL_LIST}@test.com.
Note that it DOES work in an free-style software project.
So, it does not work within hudson.maven.reporters.MavenMailer, but it does
work within hudson.tasks.Mailer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13277) Global environment variables are not being resolved in Email Notification Recipients list for maven 2/3 projects
[
https://issues.jenkins-ci.org/browse/JENKINS-13277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161526#comment-161526
]
Slide-O-Mix commented on JENKINS-13277:
---
Email Notification is not the email-ext plugin.
Global environment variables are not being resolved in Email Notification
Recipients list for maven 2/3 projects
Key: JENKINS-13277
URL: https://issues.jenkins-ci.org/browse/JENKINS-13277
Project: Jenkins
Issue Type: Bug
Components: email-ext, notification
Affects Versions: current
Reporter: jfreej
When using a global environment variable, defined in Manage Jenkins
Configure System Environment Variables (e.g. ALERT_EMAIL_LIST), in the
Email Notification Recipients list of a maven 2/3 project (e.g.
${ALERT_EMAIL_LIST}) the environment variable is not resolved. In the
console output we see: Sending e-mails to: ${ALERT_EMAIL_LIST}@test.com.
Note that it DOES work in an free-style software project.
So, it does not work within hudson.maven.reporters.MavenMailer, but it does
work within hudson.tasks.Mailer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13277) Global environment variables are not being resolved in Email Notification Recipients list for maven 2/3 projects
jfreej created JENKINS-13277:
Summary: Global environment variables are not being resolved in
Email Notification Recipients list for maven 2/3 projects
Key: JENKINS-13277
URL: https://issues.jenkins-ci.org/browse/JENKINS-13277
Project: Jenkins
Issue Type: Bug
Components: email-ext, notification
Affects Versions: current
Reporter: jfreej
When using a global environment variable, defined in Manage Jenkins
Configure System Environment Variables (e.g. ALERT_EMAIL_LIST), in the
Email Notification Recipients list of a maven 2/3 project (e.g.
${ALERT_EMAIL_LIST}) the environment variable is not resolved. In the console
output we see: Sending e-mails to: ${ALERT_EMAIL_LIST}@test.com.
Note that it DOES work in an free-style software project.
So, it does not work within hudson.maven.reporters.MavenMailer, but it does
work within hudson.tasks.Mailer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
