Environment variables work fine, you use the ENV token like ${ENV, var="YOURVAR"}. You could also use a presend script to modify the recipient list using a groovy script. See the wiki for more info.
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Environment variables work fine, you use the ENV token like ${ENV, var="YOURVAR"}. You could also use a presend script to modify the recipient list using a groovy script. See the wiki for more info.
No, its been around for a long time and works for me just fine. It may depend on how you are setting the env variable. Ones that are set by build steps are not retained by Jenkins (nothing to do with email-ext) so keep that in mind.
No, its been around for a long time and works for me just fine. It may depend on how you are setting the env variable. Ones that are set by build steps are not retained by Jenkins (nothing to do with email-ext) so keep that in mind.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e5569eb9-6fb2-4aec-8fc2-f08b7bcd7b2c%40googlegroups.com.
import javax.mail.Message.RecipientType
import javax.mail.Address
import javax.mail.internet.InternetAddress
import javax.mail.internet.MimeMessage
if ("${ENV,var="PROJECT_ADMIN_MAIL"}") {
msg.setFrom(new InternetAddress("${ENV,var="PROJECT_ADMIN_MAIL"}"))
}