Interesting-- it does not. Does that mean my syntax for BUILD_LOG_REGEX is
broken? If so, how? It appears correct based upon what the documentation
expects...
-- Corey
On Wednesday, August 29, 2012 12:13:21 PM UTC-7, slide wrote:
>
> Let me try something locally...it should be working. Does it work if you
> put it into the content area?
>
> Sent from my Windows Phone
> ------------------------------
> From: Corey Quinn
> Sent: 8/29/2012 11:55 AM
> To: jenkins...@googlegroups.com <javascript:>
> Subject: Re: Macros not being expanded properly
>
> Currently 2.24.1.
>
> -- Corey
>
> On Wednesday, August 29, 2012 11:20:20 AM UTC-7, slide wrote:
>>
>> What version of email-ext are you using?
>>
>> On Wed, Aug 29, 2012 at 11:17 AM, Corey Quinn <co...@sequestered.net>
>> wrote:
>> > I'm using the Jenkins Email Extension Plugin to send custom email
>> > notifications.
>> >
>> > I have a line in my buildlog (right near the top) that spits out "The
>> hash
>> > is:" followed by the full git hash.
>> >
>> > The subject I've set for this job is:
>> > d0 release of ${BUILD_LOG_REGEX, regex='The hash is ([a-f0-9]+)',
>> > substText=1}, which isn't being evaluated, but rather literally quoted.
>> >
>> > However, the body expands macros properly, including $DEFAULT_CONTENT
>> and
>> > ${BUILD_LOG}.
>> >
>> > Do I have something misconfigured, or is this a known issue?
>> >
>> > -- Corey
>>
>>
>>
>> --
>> Website: http://earl-of-code.com
>>
>
