Thanks-- missed that!
It worked better than before-- the expression is at least being evaluated:
d0 release of [...truncated 11 lines...]
and then it munges the MIME encoding.
Do I have to throw in an EOL character somehow, or is my regexp ill
conceived to match on:
The hash is 894a07d61e5a521008091fbf74957217378d3d60. (and yes, that period
at the end of the hash is present-- removing it makes no discernable
difference)
On Wednesday, August 29, 2012 4:07:28 PM UTC-7, slide wrote:
>
> Please copy exactly what I typed in my email and use that.
>
> On Wed, Aug 29, 2012 at 4:00 PM, Corey Quinn
> <co...@sequestered.net<javascript:>>
> wrote:
> > Hmm. Same issue:
> >
> > d0 release of ${BUILD_LOG_REGEX,regex="The hash is
> > ([a-f0-9]+)",substText=$1}
> >
> >
> > On Wednesday, August 29, 2012 2:33:33 PM UTC-7, slide wrote:
> >>
> >> Do you have single quotes as is shown below? Please use double quotes,
> >> and make sure that the value for substText also has double quotes:
> >>
> >> ${BUILD_LOG_REGEX, regex="The hash is ([a-f0-9]+)", substText="$1"}
> >>
> >>
> >>
> >> On Wed, Aug 29, 2012 at 2:15 PM, Corey Quinn <co...@sequestered.net>
> >> wrote:
> >> > Hmm.
> >> > d0 release of ${BUILD_LOG_REGEX,regex='The hash is
> >> > ([a-f0-9]+)',substText=$1}
> >> >
> >> > That's taken straight from the subject, changing 1 to $1 didn't solve
> >> > it.
> >> >
> >> > Thoughts?
> >> >
> >> > On Aug 29, 2012, at 1:53 PM, Corey Quinn <co...@sequestered.net>
> wrote:
> >> >
> >> >> Right, except that I want just the hash, not the entire line.
> >> >>
> >> >> -- Corey
> >> >> On Aug 29, 2012, at 1:53 PM, Slide <slide...@gmail.com> wrote:
> >> >>
> >> >>> I think you want something like this:
> >> >>>
> >> >>> ${BUILD_LOG_REGEX, regex='The hash is ([a-f0-9]+)', substText="$1"}
> >> >>>
> >> >>> slide
> >> >>>
> >> >>>
> >> >>> On Wed, Aug 29, 2012 at 1:44 PM, Corey Quinn <co...@sequestered.net>
>
> >> >>> wrote:
> >> >>>> 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
> >> >>>>>
> >> >>>>> 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
> >> >>>
> >> >>>
> >> >>>
> >> >>> --
> >> >>> Website: http://earl-of-code.com
> >> >>
> >> >
> >>
> >>
> >>
> >> --
> >> Website: http://earl-of-code.com
>
>
>
> --
> Website: http://earl-of-code.com
>
