On Tuesday, April 1, 2014 1:50:47 PM UTC+2, slide wrote:
>
> 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.
>

so this means there is no way for the build to affect the list of 
recipients of mail ?

I tried using tokens but they seem to only work for subject and body.

Is this somehow intentional ? 

/max

On Apr 1, 2014 4:43 AM, "Max Rydahl Andersen" 
<[email protected]<javascript:>> 
> wrote:
>
>>
>>
>> On Monday, March 31, 2014 2:56:11 PM UTC+2, slide wrote:
>>>
>>> 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, the ${ENV style does not work in the body nor recipient list.
>>
>> I guess I could try the groovy script approach - but would be simpler if 
>> mail-ext actually supported the env variables as claimed. Maybe it was 
>> added very late and I don't have latest update ?
>>
>> /max
>>
>> On Mar 31, 2014 1:24 AM, "Max Rydahl Andersen" <[email protected]> 
>>> wrote:
>>>
>>>> I found this issue: https://issues.jenkins-ci.org/browse/JENKINS-5942
>>>>
>>>> it was closed as incomplete but as far as I can see it is exactly the 
>>>> problem - not possible to access environment variables set by the build in 
>>>> the actual mail.
>>>>
>>>>
>>>> On Monday, March 31, 2014 8:16:41 AM UTC+2, Max Rydahl Andersen wrote:
>>>>>
>>>>> Hey,
>>>>>
>>>>> Background:
>>>>> I got a little script (https://github.com/maxandersen/jiralint) which 
>>>>> is used to take queries against Jira locating stale jiras or jiras with 
>>>>> missing/wrong information on them
>>>>> and then generate a junit test xml report which then in turn makes 
>>>>> jenkins generate a build failure report. Been working great for years but 
>>>>> until now
>>>>> even I can identifiy the individuals who needs to react for now the 
>>>>> build failure just been blasted out to the whole team.
>>>>>
>>>>> I would like to change/fix that.
>>>>>
>>>>> Question:
>>>>> Is it possible by the build itself to change the recipients of the 
>>>>> mail(ext) plugin ?
>>>>>
>>>>> a) either by using an environment variable
>>>>> b) contributing to the list of culprits 
>>>>>
>>>>> For #A I've only seen it allow build paramters - that is not enough 
>>>>> since I don't know the set of recipients before the build have completed.
>>>>> For #B I've only found a way to change that is to implement a fork of 
>>>>> the git plugin but I would prefer I could simply add/change the list of 
>>>>> culprits if possible.
>>>>>
>>>>> Any ideas/suggestions to the above that does not require *too* exotic 
>>>>> plugins ? :)
>>>>>
>>>>> Thanks,
>>>>> /max
>>>>>
>>>>  -- 
>>>> 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 [email protected].
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>  -- 
>> 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 [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to