subject:"tidying up Ext\-email output"

RE: tidying up Ext-email output

2016-06-14 Thread Ginga, Dick

Thanks muchly

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Slide
Sent: Tuesday, June 14, 2016 11:42 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: tidying up Ext-email output

Ok, I think you actually want your regex to be this: (?i)(?:.*)(FAIL:.*)

The substText option replaces the content of only the matching portion of the 
string, so in your case, you are replacing the exact same text in the same 
spot. The regex above will match the entire line and only give back the 
"FAIL:..." portion of the message. In regards to the expansion, I am seeing the 
correct behavior with three lines separated by newline. If you are using a 
custom template, you can use the BUILD_LOG_REGEX token INSIDE the template to 
avoid any issues with HTML tags and so forth, you just use it a little 
differently:

BUILD_LOG_REGEX(regex: '...', substText: '...')

I think you want escapeHtml to be off and put  tags inside the substText to 
separate the lines that match.

I see you changed to a different output format, so the above doesn't apply, but 
I sent the email anyway so someone else may benefit in the future.

On Tue, Jun 14, 2016 at 8:30 AM Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
Yes, I did notice that ☺

From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of Slide
Sent: Tuesday, June 14, 2016 11:29 AM

To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Re: tidying up Ext-email output

FYI, the test you did with  shows that $1 is NOT evaluating to ALL three 
lines at once, since the  is in between each one.

On Tue, Jun 14, 2016 at 8:13 AM Slide 
<slide.o@gmail.com<mailto:slide.o@gmail.com>> wrote:
I will try and test this out locally and see what I come up with.

On Tue, Jun 14, 2016 at 4:42 AM Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
Well Slide, that was just my most recent attempt at getting the output I 
desire. I am still getting this as email output (fragment):

CHANGES

No Changes

*** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT

From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of Slide
Sent: Monday, June 13, 2016 9:07 PM

To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Re: tidying up Ext-email output

This would create two body elements in the email, not sure how that will affect 
things.

On Mon, Jun 13, 2016, 04:32 Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
I am using a template for the bulk of the email (attached). The actual Email 
Default Content field contains (at the moment)

$DEFAULT_CONTENT

${BUILD_LOG_REGEX, regex="(?i)( FAIL:.*)", escapeHtml=true, substText="$1", 
showTruncatedLines=false, escapeHtml=true}

Thanks for your help.

From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of Slide
Sent: Friday, June 10, 2016 7:22 PM

To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Re: tidying up Ext-email output

Are you using a template for this? Or are you generating everything by hand 
using content tokens? If you are using a template, can you send it?

On Fri, Jun 10, 2016 at 11:16 AM Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
I don’t know what you consider large, but it all looks more or less like this:

13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: Coor

Re: tidying up Ext-email output

2016-06-14 Thread Slide

Ok, I think you actually want your regex to be this: (?i)(?:.*)(FAIL:.*)

The substText option replaces the content of only the matching portion of
the string, so in your case, you are replacing the exact same text in the
same spot. The regex above will match the entire line and only give back
the "FAIL:..." portion of the message. In regards to the expansion, I am
seeing the correct behavior with three lines separated by newline. If you
are using a custom template, you can use the BUILD_LOG_REGEX token INSIDE
the template to avoid any issues with HTML tags and so forth, you just use
it a little differently:

BUILD_LOG_REGEX(regex: '...', substText: '...')

I think you want escapeHtml to be off and put  tags inside the
substText to separate the lines that match.

I see you changed to a different output format, so the above doesn't apply,
but I sent the email anyway so someone else may benefit in the future.

On Tue, Jun 14, 2016 at 8:30 AM Ginga, Dick <dick.gi...@perkinelmer.com>
wrote:

> Yes, I did notice that J
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Slide
> *Sent:* Tuesday, June 14, 2016 11:29 AM
>
>
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: tidying up Ext-email output
>
>
>
> FYI, the test you did with  shows that $1 is NOT evaluating to ALL
> three lines at once, since the  is in between each one.
>
>
>
> On Tue, Jun 14, 2016 at 8:13 AM Slide <slide.o@gmail.com> wrote:
>
> I will try and test this out locally and see what I come up with.
>
>
>
> On Tue, Jun 14, 2016 at 4:42 AM Ginga, Dick <dick.gi...@perkinelmer.com>
> wrote:
>
> Well Slide, that was just my most recent attempt at getting the output I
> desire. I am still getting this as email output (fragment):
>
>
>
>
>
> *CHANGES*
>
> No Changes
>
>
>
> *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST *** FAIL:
> LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER *** FAIL:
> LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT
>
>
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Slide
> *Sent:* Monday, June 13, 2016 9:07 PM
>
>
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: tidying up Ext-email output
>
>
>
> This would create two body elements in the email, not sure how that will
> affect things.
>
>
>
> On Mon, Jun 13, 2016, 04:32 Ginga, Dick <dick.gi...@perkinelmer.com>
> wrote:
>
> I am using a template for the bulk of the email (attached). The actual
> Email Default Content field contains (at the moment)
>
>
>
> $DEFAULT_CONTENT
>
>
>
> 
>
>
>
> ${BUILD_LOG_REGEX, regex="(?i)( FAIL:.*)", escapeHtml=true,
> substText="$1", showTruncatedLines=false, escapeHtml=true}
>
>
>
> 
>
>
>
> Thanks for your help.
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Slide
> *Sent:* Friday, June 10, 2016 7:22 PM
>
>
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: tidying up Ext-email output
>
>
>
> Are you using a template for this? Or are you generating everything by
> hand using content tokens? If you are using a template, can you send it?
>
>
>
> On Fri, Jun 10, 2016 at 11:16 AM Ginga, Dick <dick.gi...@perkinelmer.com>
> wrote:
>
> I don’t know what you consider large, but it all looks more or less like
> this:
>
>
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: m_at [0] != kccNoAb &&

RE: tidying up Ext-email output

2016-06-14 Thread Ginga, Dick

Hey Slide, if you would like to pursue this for academic reasons, feel free, 
but, we have just changed our tests to produce Junit formatted XML output and 
now my email looks like this. so I can now get rid of my attempt at capturing 
console test results.

Thanks a LOT for your help. I mean it.


CHANGES

No Changes



JUnit Tests

Name: (root) Failed: 3 test(s), Passed: 37 test(s), Skipped: 0 test(s), Total: 
40 test(s)

•  Failed: LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER

•  Failed: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST

•  Failed: LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT



*** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Slide
Sent: Tuesday, June 14, 2016 11:29 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: tidying up Ext-email output

FYI, the test you did with  shows that $1 is NOT evaluating to ALL three 
lines at once, since the  is in between each one.

On Tue, Jun 14, 2016 at 8:13 AM Slide 
<slide.o@gmail.com<mailto:slide.o@gmail.com>> wrote:
I will try and test this out locally and see what I come up with.

On Tue, Jun 14, 2016 at 4:42 AM Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
Well Slide, that was just my most recent attempt at getting the output I 
desire. I am still getting this as email output (fragment):


CHANGES

No Changes



*** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT


From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of Slide
Sent: Monday, June 13, 2016 9:07 PM

To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Re: tidying up Ext-email output


This would create two body elements in the email, not sure how that will affect 
things.

On Mon, Jun 13, 2016, 04:32 Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
I am using a template for the bulk of the email (attached). The actual Email 
Default Content field contains (at the moment)

$DEFAULT_CONTENT



${BUILD_LOG_REGEX, regex="(?i)( FAIL:.*)", escapeHtml=true, substText="$1", 
showTruncatedLines=false, escapeHtml=true}



Thanks for your help.

From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of Slide
Sent: Friday, June 10, 2016 7:22 PM

To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Re: tidying up Ext-email output

Are you using a template for this? Or are you generating everything by hand 
using content tokens? If you are using a template, can you send it?

On Fri, Jun 10, 2016 at 11:16 AM Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
I don’t know what you consider large, but it all looks more or less like this:

13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: m_at [0] != kccNoAb && m_at [0] < m_at [1] && m_at 
[1] < m_at [2] && (m_at [2] < m_at [3] || m_at [3] == kccNoAb) at line: 210, 
file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libcc\src\cc_stereo.cpp
13:08:49*** Value of: (int)queryHitSet.NumHits() |   Actual: 17 | Expected: 
numExpected | Which is: 1 | Hit count  failed for: test1.cdxml
13:08:49*** Value of: (int)queryHitSet2.NumHits() |   Actual: 17 | 
Expected: numExpected | Which is: 1 | Hit count2 failed for: test1.cdxml
13:08:49 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITC

Re: tidying up Ext-email output

2016-06-14 Thread Slide

FYI, the test you did with  shows that $1 is NOT evaluating to ALL
three lines at once, since the  is in between each one.

On Tue, Jun 14, 2016 at 8:13 AM Slide <slide.o@gmail.com> wrote:

> I will try and test this out locally and see what I come up with.
>
> On Tue, Jun 14, 2016 at 4:42 AM Ginga, Dick <dick.gi...@perkinelmer.com>
> wrote:
>
>> Well Slide, that was just my most recent attempt at getting the output I
>> desire. I am still getting this as email output (fragment):
>>
>>
>>
>>
>>
>> *CHANGES*
>>
>> No Changes
>>
>>
>>
>>
>> *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST *** FAIL:
>> LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER *** FAIL:
>> LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT
>>
>>
>>
>>
>>
>> *From:* jenkinsci-users@googlegroups.com [mailto:
>> jenkinsci-users@googlegroups.com] *On Behalf Of *Slide
>> *Sent:* Monday, June 13, 2016 9:07 PM
>>
>>
>> *To:* jenkinsci-users@googlegroups.com
>> *Subject:* Re: tidying up Ext-email output
>>
>>
>>
>> This would create two body elements in the email, not sure how that will
>> affect things.
>>
>>
>>
>> On Mon, Jun 13, 2016, 04:32 Ginga, Dick <dick.gi...@perkinelmer.com>
>> wrote:
>>
>> I am using a template for the bulk of the email (attached). The actual
>> Email Default Content field contains (at the moment)
>>
>>
>>
>> $DEFAULT_CONTENT
>>
>>
>>
>> 
>>
>>
>>
>> ${BUILD_LOG_REGEX, regex="(?i)( FAIL:.*)", escapeHtml=true,
>> substText="$1", showTruncatedLines=false, escapeHtml=true}
>>
>>
>>
>> 
>>
>>
>>
>> Thanks for your help.
>>
>>
>>
>> *From:* jenkinsci-users@googlegroups.com [mailto:
>> jenkinsci-users@googlegroups.com] *On Behalf Of *Slide
>> *Sent:* Friday, June 10, 2016 7:22 PM
>>
>>
>> *To:* jenkinsci-users@googlegroups.com
>> *Subject:* Re: tidying up Ext-email output
>>
>>
>>
>> Are you using a template for this? Or are you generating everything by
>> hand using content tokens? If you are using a template, can you send it?
>>
>>
>>
>> On Fri, Jun 10, 2016 at 11:16 AM Ginga, Dick <dick.gi...@perkinelmer.com>
>> wrote:
>>
>> I don’t know what you consider large, but it all looks more or less like
>> this:
>>
>>
>>
>> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
>> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>>
>> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
>> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>>
>> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
>> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>>
>> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
>> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>>
>> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
>> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>>
>> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
>> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>>
>> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
>> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>>
>> *13:08:49* CORE CHEM ERROR: m_at [0] != kccNoAb && m_at [0] < m_at [1]
>> && m_at [1] < m_at [2] && (m_at [2] < m_at [3] || m_at [3] == kccNoAb) at
>> line: 210, file:
>> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libcc\src\cc_stereo.cpp
>>
>> *13:08:49**** Value of: (int)queryHitSet.NumHits() |   Actual: 17 |
>> Expected: numExpected | Which is: 1 | Hit count  failed for: test1.cdxml
>>
>> *13:08:49**** Value of: (int)queryHitSet2.NumHits() |   Actual: 17 |
>> Expected: numExpected | Which is: 1 | Hit count2 failed for: test1.cdxml
>>
>> *13:08:49* *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST
>>
>> *13:08:49* *** Starting test LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER
>>
>> *13:08:49* CORE CHEM ERROR: m_fQuery || sopts.FullStruct() at line: 420,
>> file:
>> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libc

RE: tidying up Ext-email output

2016-06-14 Thread Ginga, Dick

Yes, I did notice that ☺

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Slide
Sent: Tuesday, June 14, 2016 11:29 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: tidying up Ext-email output

FYI, the test you did with  shows that $1 is NOT evaluating to ALL three 
lines at once, since the  is in between each one.

On Tue, Jun 14, 2016 at 8:13 AM Slide 
<slide.o@gmail.com<mailto:slide.o@gmail.com>> wrote:
I will try and test this out locally and see what I come up with.

On Tue, Jun 14, 2016 at 4:42 AM Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
Well Slide, that was just my most recent attempt at getting the output I 
desire. I am still getting this as email output (fragment):


CHANGES

No Changes



*** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT


From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of Slide
Sent: Monday, June 13, 2016 9:07 PM

To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Re: tidying up Ext-email output


This would create two body elements in the email, not sure how that will affect 
things.

On Mon, Jun 13, 2016, 04:32 Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
I am using a template for the bulk of the email (attached). The actual Email 
Default Content field contains (at the moment)

$DEFAULT_CONTENT



${BUILD_LOG_REGEX, regex="(?i)( FAIL:.*)", escapeHtml=true, substText="$1", 
showTruncatedLines=false, escapeHtml=true}



Thanks for your help.

From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of Slide
Sent: Friday, June 10, 2016 7:22 PM

To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Re: tidying up Ext-email output

Are you using a template for this? Or are you generating everything by hand 
using content tokens? If you are using a template, can you send it?

On Fri, Jun 10, 2016 at 11:16 AM Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
I don’t know what you consider large, but it all looks more or less like this:

13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: m_at [0] != kccNoAb && m_at [0] < m_at [1] && m_at 
[1] < m_at [2] && (m_at [2] < m_at [3] || m_at [3] == kccNoAb) at line: 210, 
file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libcc\src\cc_stereo.cpp
13:08:49*** Value of: (int)queryHitSet.NumHits() |   Actual: 17 | Expected: 
numExpected | Which is: 1 | Hit count  failed for: test1.cdxml
13:08:49*** Value of: (int)queryHitSet2.NumHits() |   Actual: 17 | 
Expected: numExpected | Which is: 1 | Hit count2 failed for: test1.cdxml
13:08:49 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST
13:08:49 *** Starting test LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER
13:08:49 CORE CHEM ERROR: m_fQuery || sopts.FullStruct() at line: 420, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libcc\src\cc_screens.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:

Re: tidying up Ext-email output

2016-06-14 Thread Slide

I will try and test this out locally and see what I come up with.

On Tue, Jun 14, 2016 at 4:42 AM Ginga, Dick <dick.gi...@perkinelmer.com>
wrote:

> Well Slide, that was just my most recent attempt at getting the output I
> desire. I am still getting this as email output (fragment):
>
>
>
>
>
> *CHANGES*
>
> No Changes
>
>
>
>
> *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST *** FAIL:
> LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER *** FAIL:
> LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT
>
>
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Slide
> *Sent:* Monday, June 13, 2016 9:07 PM
>
>
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: tidying up Ext-email output
>
>
>
> This would create two body elements in the email, not sure how that will
> affect things.
>
>
>
> On Mon, Jun 13, 2016, 04:32 Ginga, Dick <dick.gi...@perkinelmer.com>
> wrote:
>
> I am using a template for the bulk of the email (attached). The actual
> Email Default Content field contains (at the moment)
>
>
>
> $DEFAULT_CONTENT
>
>
>
> 
>
>
>
> ${BUILD_LOG_REGEX, regex="(?i)( FAIL:.*)", escapeHtml=true,
> substText="$1", showTruncatedLines=false, escapeHtml=true}
>
>
>
> 
>
>
>
> Thanks for your help.
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Slide
> *Sent:* Friday, June 10, 2016 7:22 PM
>
>
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: tidying up Ext-email output
>
>
>
> Are you using a template for this? Or are you generating everything by
> hand using content tokens? If you are using a template, can you send it?
>
>
>
> On Fri, Jun 10, 2016 at 11:16 AM Ginga, Dick <dick.gi...@perkinelmer.com>
> wrote:
>
> I don’t know what you consider large, but it all looks more or less like
> this:
>
>
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: m_at [0] != kccNoAb && m_at [0] < m_at [1] &&
> m_at [1] < m_at [2] && (m_at [2] < m_at [3] || m_at [3] == kccNoAb) at
> line: 210, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libcc\src\cc_stereo.cpp
>
> *13:08:49**** Value of: (int)queryHitSet.NumHits() |   Actual: 17 |
> Expected: numExpected | Which is: 1 | Hit count  failed for: test1.cdxml
>
> *13:08:49**** Value of: (int)queryHitSet2.NumHits() |   Actual: 17 |
> Expected: numExpected | Which is: 1 | Hit count2 failed for: test1.cdxml
>
> *13:08:49* *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST
>
> *13:08:49* *** Starting test LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER
>
> *13:08:49* CORE CHEM ERROR: m_fQuery || sopts.FullStruct() at line: 420,
> file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libcc\src\cc_screens.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49*

RE: tidying up Ext-email output

2016-06-14 Thread Ginga, Dick

Well Slide, that was just my most recent attempt at getting the output I 
desire. I am still getting this as email output (fragment):



CHANGES

No Changes




*** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Slide
Sent: Monday, June 13, 2016 9:07 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: tidying up Ext-email output


This would create two body elements in the email, not sure how that will affect 
things.

On Mon, Jun 13, 2016, 04:32 Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
I am using a template for the bulk of the email (attached). The actual Email 
Default Content field contains (at the moment)

$DEFAULT_CONTENT



${BUILD_LOG_REGEX, regex="(?i)( FAIL:.*)", escapeHtml=true, substText="$1", 
showTruncatedLines=false, escapeHtml=true}



Thanks for your help.

From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of Slide
Sent: Friday, June 10, 2016 7:22 PM

To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Re: tidying up Ext-email output

Are you using a template for this? Or are you generating everything by hand 
using content tokens? If you are using a template, can you send it?

On Fri, Jun 10, 2016 at 11:16 AM Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
I don’t know what you consider large, but it all looks more or less like this:

13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: m_at [0] != kccNoAb && m_at [0] < m_at [1] && m_at 
[1] < m_at [2] && (m_at [2] < m_at [3] || m_at [3] == kccNoAb) at line: 210, 
file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libcc\src\cc_stereo.cpp
13:08:49*** Value of: (int)queryHitSet.NumHits() |   Actual: 17 | Expected: 
numExpected | Which is: 1 | Hit count  failed for: test1.cdxml
13:08:49*** Value of: (int)queryHitSet2.NumHits() |   Actual: 17 | 
Expected: numExpected | Which is: 1 | Hit count2 failed for: test1.cdxml
13:08:49 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST
13:08:49 *** Starting test LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER
13:08:49 CORE CHEM ERROR: m_fQuery || sopts.FullStruct() at line: 420, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libcc\src\cc_screens.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp


From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of Slide
Sent: Friday, June 10, 2016 2:11 PM

To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Re: tidying up Ext-email

RE: tidying up Ext-email output

2016-06-13 Thread Ginga, Dick

I am using a template for the bulk of the email (attached). The actual Email 
Default Content field contains (at the moment)

$DEFAULT_CONTENT



${BUILD_LOG_REGEX, regex="(?i)( FAIL:.*)", escapeHtml=true, substText="$1", 
showTruncatedLines=false, escapeHtml=true}



Thanks for your help.

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Slide
Sent: Friday, June 10, 2016 7:22 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: tidying up Ext-email output

Are you using a template for this? Or are you generating everything by hand 
using content tokens? If you are using a template, can you send it?

On Fri, Jun 10, 2016 at 11:16 AM Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
I don’t know what you consider large, but it all looks more or less like this:

13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: m_at [0] != kccNoAb && m_at [0] < m_at [1] && m_at 
[1] < m_at [2] && (m_at [2] < m_at [3] || m_at [3] == kccNoAb) at line: 210, 
file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libcc\src\cc_stereo.cpp
13:08:49*** Value of: (int)queryHitSet.NumHits() |   Actual: 17 | Expected: 
numExpected | Which is: 1 | Hit count  failed for: test1.cdxml
13:08:49*** Value of: (int)queryHitSet2.NumHits() |   Actual: 17 | 
Expected: numExpected | Which is: 1 | Hit count2 failed for: test1.cdxml
13:08:49 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST
13:08:49 *** Starting test LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER
13:08:49 CORE CHEM ERROR: m_fQuery || sopts.FullStruct() at line: 420, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libcc\src\cc_screens.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp


From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of Slide
Sent: Friday, June 10, 2016 2:11 PM

To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Re: tidying up Ext-email output

Can you supply a larger amount of test from the build log that I can try 
locally?

On Fri, Jun 10, 2016 at 11:01 AM Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
The complete source of the email is:

meta http-equiv="Content-Type" content="text/html; charset=utf-8">
BODY, TABLE, TD, TH, P {
  font-family:Verdana,Helvetica,sans serif;
  font-size:11px;
  color:black;
}
h1 { color:black; }
h2 { color:black; }
h3 { color:black; }
TD.bg1 { color:white; background-color:#C0; font-size:120% }
TD.bg2 { color:white; background-color:#4040FF; font-size:110% }
TD.bg3 { color:white; background-color:#8080FF; }
TD.test_passed { color:blue; }
TD.test_failed { color:red; }
TD.console { font-family:Courier New; }






  http:///static/e59dfe28/images/32x32/

Re: tidying up Ext-email output

2016-06-10 Thread Slide

Are you using a template for this? Or are you generating everything by hand
using content tokens? If you are using a template, can you send it?

On Fri, Jun 10, 2016 at 11:16 AM Ginga, Dick <dick.gi...@perkinelmer.com>
wrote:

> I don’t know what you consider large, but it all looks more or less like
> this:
>
>
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: m_at [0] != kccNoAb && m_at [0] < m_at [1] &&
> m_at [1] < m_at [2] && (m_at [2] < m_at [3] || m_at [3] == kccNoAb) at
> line: 210, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libcc\src\cc_stereo.cpp
>
> *13:08:49**** Value of: (int)queryHitSet.NumHits() |   Actual: 17 |
> Expected: numExpected | Which is: 1 | Hit count  failed for: test1.cdxml
>
> *13:08:49**** Value of: (int)queryHitSet2.NumHits() |   Actual: 17 |
> Expected: numExpected | Which is: 1 | Hit count2 failed for: test1.cdxml
>
> *13:08:49* *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST
>
> *13:08:49* *** Starting test LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER
>
> *13:08:49* CORE CHEM ERROR: m_fQuery || sopts.FullStruct() at line: 420,
> file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libcc\src\cc_screens.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
> *13:08:49* CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file:
> c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
>
>
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Slide
> *Sent:* Friday, June 10, 2016 2:11 PM
>
>
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: tidying up Ext-email output
>
>
>
> Can you supply a larger amount of test from the build log that I can try
> locally?
>
>
>
> On Fri, Jun 10, 2016 at 11:01 AM Ginga, Dick <dick.gi...@perkinelmer.com>
> wrote:
>
> The complete source of the email is:
>
>
>
> meta http-equiv="Content-Type" content="text/html; charset=utf-8">
>
> BODY, TABLE, TD, TH, P {
>
>   font-family:Verdana,Helvetica,sans serif;
>
>   font-size:11px;
>
>   color:black;
>
> }
>
> h1 { color:black; }
>
> h2 { color:black; }
>
> h3 { color:black; }
>
> TD.bg1 { color:white; background-color:#C0; font-size:120% }
>
> TD.bg2 { color:white; background-color:#4040FF; font-size:110% }
>
> TD.bg3 { color:white; background-color:#8080FF; }
>
> TD.test_passed { color:blue; }
>
> TD.test_failed { color:red; }
>
> TD.console { font-family:Courier New; }
>
> 
>
> 
>
>
>
>
>
>
>
> 
>
>   http:///static/e59dfe28/images/32x32/yellow.gif
> <https://urldefense.proofpoint.com/v2/url?u=http-3A___static_e59

RE: tidying up Ext-email output

2016-06-10 Thread Ginga, Dick

I don’t know what you consider large, but it all looks more or less like this:

13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: m_at [0] != kccNoAb && m_at [0] < m_at [1] && m_at 
[1] < m_at [2] && (m_at [2] < m_at [3] || m_at [3] == kccNoAb) at line: 210, 
file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libcc\src\cc_stereo.cpp
13:08:49*** Value of: (int)queryHitSet.NumHits() |   Actual: 17 | Expected: 
numExpected | Which is: 1 | Hit count  failed for: test1.cdxml
13:08:49*** Value of: (int)queryHitSet2.NumHits() |   Actual: 17 | 
Expected: numExpected | Which is: 1 | Hit count2 failed for: test1.cdxml
13:08:49 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST
13:08:49 *** Starting test LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER
13:08:49 CORE CHEM ERROR: m_fQuery || sopts.FullStruct() at line: 420, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libcc\src\cc_screens.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp
13:08:49 CORE CHEM ERROR: CoordsAvail (a1, a2, a3) at line: 815, file: 
c:\builds\workspace\build-run-commoncs-tests-win\commoncs\libsdg\src\sdg_chains.cpp


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Slide
Sent: Friday, June 10, 2016 2:11 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: tidying up Ext-email output

Can you supply a larger amount of test from the build log that I can try 
locally?

On Fri, Jun 10, 2016 at 11:01 AM Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
The complete source of the email is:

meta http-equiv="Content-Type" content="text/html; charset=utf-8">
BODY, TABLE, TD, TH, P {
  font-family:Verdana,Helvetica,sans serif;
  font-size:11px;
  color:black;
}
h1 { color:black; }
h2 { color:black; }
h3 { color:black; }
TD.bg1 { color:white; background-color:#C0; font-size:120% }
TD.bg2 { color:white; background-color:#4040FF; font-size:110% }
TD.bg3 { color:white; background-color:#8080FF; }
TD.test_passed { color:blue; }
TD.test_failed { color:red; }
TD.console { font-family:Courier New; }






  http:///static/e59dfe28/images/32x32/yellow.gif<https://urldefense.proofpoint.com/v2/url?u=http-3A___static_e59dfe28_images_32x32_yellow.gif=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=Ed_uTOPTHkaoXVrxrcWuAEL73JsnB5Tth1iA3qnCFTc=LVhFRFwkmHQW14GxJ7qFC_WRZpiZNXxw-Eu_wxReoVA=>">
  BUILD 
UNSTABLE
  Build URLhttp:///job/Build-Run-CommonCS-Tests-Win/13/<https://urldefense.proofpoint.com/v2/url?u=http-3A___job_Build-2DRun-2DCommonCS-2DTests-2DWin_13_=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=Ed_uTOPTHkaoXVrxrcWuAEL73JsnB5Tth1iA3qnCFTc=GpVrIQB81ArBl4Zlv-qOSsFDCDmCfcqjBaHSkmtC8Fw=>">http:///job/Build-Run-CommonCS-Tests-Win/13/<https://urldefense.proofpoint.com/v2/url?u=http-3A___job_Build-2DRun-2DCommonCS-2DTests-2DWin_13_=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=Ed_uTOPTHkaoXVrxrcWuA

Re: tidying up Ext-email output

2016-06-10 Thread Slide

Can you supply a larger amount of test from the build log that I can try
locally?

On Fri, Jun 10, 2016 at 11:01 AM Ginga, Dick <dick.gi...@perkinelmer.com>
wrote:

> The complete source of the email is:
>
>
>
> meta http-equiv="Content-Type" content="text/html; charset=utf-8">
>
> BODY, TABLE, TD, TH, P {
>
>   font-family:Verdana,Helvetica,sans serif;
>
>   font-size:11px;
>
>   color:black;
>
> }
>
> h1 { color:black; }
>
> h2 { color:black; }
>
> h3 { color:black; }
>
> TD.bg1 { color:white; background-color:#C0; font-size:120% }
>
> TD.bg2 { color:white; background-color:#4040FF; font-size:110% }
>
> TD.bg3 { color:white; background-color:#8080FF; }
>
> TD.test_passed { color:blue; }
>
> TD.test_failed { color:red; }
>
> TD.console { font-family:Courier New; }
>
> 
>
> 
>
>
>
>
>
>
>
> 
>
>   http:///static/e59dfe28/images/32x32/yellow.gif;>
>
>   BUILD
> UNSTABLE
>
>   Build URLhttp:///job/Build-Run-CommonCS-Tests-Win/13/;>
> http:///job/Build-Run-CommonCS-Tests-Win/13/
>
>   Build Loghttp:///job/Build-Run-CommonCS-Tests-Win/13/console;>
> http:///job/Build-Run-CommonCS-Tests-Win/13/console
>
>   Project:Build-Run-CommonCS-Tests-Win
>
>   Date of build:Fri, 10 Jun 2016 13:05:06 -0400
>
>   Build duration:30 min
>
>   Stream:null
>
>   Build Number:13
>
>   Build Type:null
>
> 
>
> 
>
>
>
> 
>
>
>
> 
>
> CHANGES
>
>
>
> No Changes
>
>
>
>   
>
> 
>
>
>
>
>
> 
>
>
>
>
>
> 
>
>
>
>
>
> 
>
>
>
>
>
>   
>
> 
>
>
>
> 
>
>
>
>
>
> 
>
>
>
>
>
>
>
> 
>
>
>
> ***br FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST
>
> ***br FAIL: LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER
>
> ***br FAIL: LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT
>
>
>
>
>
> 
>
>
>
> *From:* Ginga, Dick
> *Sent:* Friday, June 10, 2016 1:57 PM
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* RE: tidying up Ext-email output
>
>
>
> I have tried  and escaped and not escaped HTML and  … 
> around my build-log-regex and I get this:
>
>
>
> *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST *** FAIL:
> LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER *** FAIL:
> LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT
>
>
>
>
>
>
>
> *From:* jenkinsci-users@googlegroups.com [
> mailto:jenkinsci-users@googlegroups.com <jenkinsci-users@googlegroups.com>]
> *On Behalf Of *Slide
> *Sent:* Friday, June 10, 2016 11:20 AM
>
>
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: tidying up Ext-email output
>
>
>
> Have you tried using  instead of \n?
>
>
>
> On Fri, Jun 10, 2016, 08:18 Ginga, Dick <dick.gi...@perkinelmer.com>
> wrote:
>
> yes
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Slide
> *Sent:* Friday, June 10, 2016 11:15 AM
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: tidying up Ext-email output
>
>
>
> Are you using html email?
>
>
>
> On Fri, Jun 10, 2016, 08:01 Ginga, Dick <dick.gi...@perkinelmer.com>
> wrote:
>
> Hello all, just trying to create a “better” email response.
>
>
>
> I have some custom written tests that produce lots of test output, but I
> only want the failures (FAIL:) in the email,
>
>
>
> *09:53:06* *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST
>
> …
>
> *09:54:09* *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER
>
> …
>
> *09:54:15* *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT
>
>
>
> so I use
>
>
>
> ${BUILD_LOG_REGEX, regex="(?i)( FAIL:.*)", substText="\n$1\n",
> showTruncatedLines=false, escapeHtml=true}
>
>
>
> But I get this,
>
>
>
> *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST *** FAIL:
> LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER *** FAIL:
> LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT
>
>
>
> I would like each of these failures to be on its own line. That is what I
> thought maybe the substText might do but apparently not.
>
>
>
> Is there a way to do this?
>
>
>
> *Dick Ginga, Informatics R*
>
> *PerkinElmer Inc. *
> *| For the Better **HUMAN HEALTH **|* *ENVIRONMENTAL HEALTH*
> 940 Winter Street, Waltham MA 02451
>
>
>
> *dick.ginga**@perkinelmer.com <ed.cof...@perkinelmer.com>*
>
> Mobile – 508-847-1434
>
> Off

RE: tidying up Ext-email output

2016-06-10 Thread Ginga, Dick

The complete source of the email is:

meta http-equiv="Content-Type" content="text/html; charset=utf-8">
BODY, TABLE, TD, TH, P {
  font-family:Verdana,Helvetica,sans serif;
  font-size:11px;
  color:black;
}
h1 { color:black; }
h2 { color:black; }
h3 { color:black; }
TD.bg1 { color:white; background-color:#C0; font-size:120% }
TD.bg2 { color:white; background-color:#4040FF; font-size:110% }
TD.bg3 { color:white; background-color:#8080FF; }
TD.test_passed { color:blue; }
TD.test_failed { color:red; }
TD.console { font-family:Courier New; }






  http:///static/e59dfe28/images/32x32/yellow.gif;>
  BUILD 
UNSTABLE
  Build URLhttp:///job/Build-Run-CommonCS-Tests-Win/13/;>http:///job/Build-Run-CommonCS-Tests-Win/13/
  Build Loghttp:///job/Build-Run-CommonCS-Tests-Win/13/console;>http:///job/Build-Run-CommonCS-Tests-Win/13/console
  Project:Build-Run-CommonCS-Tests-Win
  Date of build:Fri, 10 Jun 2016 13:05:06 -0400
  Build duration:30 min
  Stream:null
  Build Number:13
  Build Type:null






CHANGES

No Changes

  












  











***br FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST
***br FAIL: LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER
***br FAIL: LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT




From: Ginga, Dick
Sent: Friday, June 10, 2016 1:57 PM
To: jenkinsci-users@googlegroups.com
Subject: RE: tidying up Ext-email output

I have tried  and escaped and not escaped HTML and  …  around 
my build-log-regex and I get this:

*** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT



From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Slide
Sent: Friday, June 10, 2016 11:20 AM
To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Re: tidying up Ext-email output


Have you tried using  instead of \n?

On Fri, Jun 10, 2016, 08:18 Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
yes

From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of Slide
Sent: Friday, June 10, 2016 11:15 AM
To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Re: tidying up Ext-email output


Are you using html email?

On Fri, Jun 10, 2016, 08:01 Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
Hello all, just trying to create a “better” email response.

I have some custom written tests that produce lots of test output, but I only 
want the failures (FAIL:) in the email,

09:53:06 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST
…

09:54:09 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER
…

09:54:15 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT

so I use

${BUILD_LOG_REGEX, regex="(?i)( FAIL:.*)", substText="\n$1\n", 
showTruncatedLines=false, escapeHtml=true}

But I get this,

*** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT

I would like each of these failures to be on its own line. That is what I 
thought maybe the substText might do but apparently not.

Is there a way to do this?

Dick Ginga, Informatics R
PerkinElmer Inc. | For the Better
HUMAN HEALTH | ENVIRONMENTAL HEALTH
940 Winter Street, Waltham MA 02451

dick.gi...@perkinelmer.com<mailto:ed.cof...@perkinelmer.com>
Mobile – 508-847-1434
Office – 781-663-6947

--
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-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E2D8711C23%40AMERMBX02.PERKINELMER.NET<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_msgid_jenkinsci-2Dusers_6C6EE445A6F6CE4E8A0FFB51B071A4E2D8711C23-2540AMERMBX02.PERKINELMER.NET-3Futm-5Fmedium-3Demail-26utm-5Fsource-3Dfooter=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=mXByn-k5ahdwHXfgIzt1kZhAXWCuXghYTJj4IHz05lc=dglEPB15sKA_YOKPLxLdeKJ34vohwQQ8-KcqMNssCH0=>.
For more options, visit 
https://groups.google.com/d/optout<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=mXByn-k5ahdwHXfgIzt1kZhAXWCuXghYTJj4IHz05lc=N0RBCmmnoAD4p05B0Nzg5ZOj81T78N1yEGGjegZWksQ=>.
--
You received this message because you

RE: tidying up Ext-email output

2016-06-10 Thread Ginga, Dick

I have tried  and escaped and not escaped HTML and  …  around 
my build-log-regex and I get this:

*** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT



From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Slide
Sent: Friday, June 10, 2016 11:20 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: tidying up Ext-email output


Have you tried using  instead of \n?

On Fri, Jun 10, 2016, 08:18 Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
yes

From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of Slide
Sent: Friday, June 10, 2016 11:15 AM
To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Re: tidying up Ext-email output


Are you using html email?

On Fri, Jun 10, 2016, 08:01 Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
Hello all, just trying to create a “better” email response.

I have some custom written tests that produce lots of test output, but I only 
want the failures (FAIL:) in the email,

09:53:06 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST
…

09:54:09 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER
…

09:54:15 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT

so I use

${BUILD_LOG_REGEX, regex="(?i)( FAIL:.*)", substText="\n$1\n", 
showTruncatedLines=false, escapeHtml=true}

But I get this,

*** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT

I would like each of these failures to be on its own line. That is what I 
thought maybe the substText might do but apparently not.

Is there a way to do this?

Dick Ginga, Informatics R
PerkinElmer Inc. | For the Better
HUMAN HEALTH | ENVIRONMENTAL HEALTH
940 Winter Street, Waltham MA 02451

dick.gi...@perkinelmer.com<mailto:ed.cof...@perkinelmer.com>
Mobile – 508-847-1434
Office – 781-663-6947

--
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-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E2D8711C23%40AMERMBX02.PERKINELMER.NET<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_msgid_jenkinsci-2Dusers_6C6EE445A6F6CE4E8A0FFB51B071A4E2D8711C23-2540AMERMBX02.PERKINELMER.NET-3Futm-5Fmedium-3Demail-26utm-5Fsource-3Dfooter=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=mXByn-k5ahdwHXfgIzt1kZhAXWCuXghYTJj4IHz05lc=dglEPB15sKA_YOKPLxLdeKJ34vohwQQ8-KcqMNssCH0=>.
For more options, visit 
https://groups.google.com/d/optout<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=mXByn-k5ahdwHXfgIzt1kZhAXWCuXghYTJj4IHz05lc=N0RBCmmnoAD4p05B0Nzg5ZOj81T78N1yEGGjegZWksQ=>.
--
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-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVerq2uUTBOzeY8Gwp2ebPRthjObtJ_A4M%3DeU1OZtRcA1w%40mail.gmail.com<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_msgid_jenkinsci-2Dusers_CAPiUgVerq2uUTBOzeY8Gwp2ebPRthjObtJ-5FA4M-253DeU1OZtRcA1w-2540mail.gmail.com-3Futm-5Fmedium-3Demail-26utm-5Fsource-3Dfooter=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=mXByn-k5ahdwHXfgIzt1kZhAXWCuXghYTJj4IHz05lc=2ysptL8ae42kRVa5benLWvcc11wYuWJ9PXganZfAz2Y=>.

For more options, visit 
https://groups.google.com/d/optout<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=mXByn-k5ahdwHXfgIzt1kZhAXWCuXghYTJj4IHz05lc=N0RBCmmnoAD4p05B0Nzg5ZOj81T78N1yEGGjegZWksQ=>.
--
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-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d

Re: tidying up Ext-email output

2016-06-10 Thread Slide

Have you tried using  instead of \n?

On Fri, Jun 10, 2016, 08:18 Ginga, Dick <dick.gi...@perkinelmer.com> wrote:

> yes
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Slide
> *Sent:* Friday, June 10, 2016 11:15 AM
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: tidying up Ext-email output
>
>
>
> Are you using html email?
>
>
>
> On Fri, Jun 10, 2016, 08:01 Ginga, Dick <dick.gi...@perkinelmer.com>
> wrote:
>
> Hello all, just trying to create a “better” email response.
>
>
>
> I have some custom written tests that produce lots of test output, but I
> only want the failures (FAIL:) in the email,
>
>
>
> *09:53:06* *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST
>
> …
>
> *09:54:09* *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER
>
> …
>
> *09:54:15* *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT
>
>
>
> so I use
>
>
>
> ${BUILD_LOG_REGEX, regex="(?i)( FAIL:.*)", substText="\n$1\n",
> showTruncatedLines=false, escapeHtml=true}
>
>
>
> But I get this,
>
>
>
> *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST *** FAIL:
> LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER *** FAIL:
> LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT
>
>
>
> I would like each of these failures to be on its own line. That is what I
> thought maybe the substText might do but apparently not.
>
>
>
> Is there a way to do this?
>
>
>
> *Dick Ginga, Informatics R*
>
> *PerkinElmer Inc. *
> *| For the Better **HUMAN HEALTH **|* *ENVIRONMENTAL HEALTH*
> 940 Winter Street, Waltham MA 02451
>
>
>
> *dick.ginga**@perkinelmer.com <ed.cof...@perkinelmer.com>*
>
> Mobile – 508-847-1434
>
> Office – 781-663-6947
>
>
>
> --
> 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-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E2D8711C23%40AMERMBX02.PERKINELMER.NET
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_msgid_jenkinsci-2Dusers_6C6EE445A6F6CE4E8A0FFB51B071A4E2D8711C23-2540AMERMBX02.PERKINELMER.NET-3Futm-5Fmedium-3Demail-26utm-5Fsource-3Dfooter=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=mXByn-k5ahdwHXfgIzt1kZhAXWCuXghYTJj4IHz05lc=dglEPB15sKA_YOKPLxLdeKJ34vohwQQ8-KcqMNssCH0=>
> .
> For more options, visit https://groups.google.com/d/optout
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=mXByn-k5ahdwHXfgIzt1kZhAXWCuXghYTJj4IHz05lc=N0RBCmmnoAD4p05B0Nzg5ZOj81T78N1yEGGjegZWksQ=>
> .
>
> --
> 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-users+unsubscr...@googlegroups.com.
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVerq2uUTBOzeY8Gwp2ebPRthjObtJ_A4M%3DeU1OZtRcA1w%40mail.gmail.com
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_msgid_jenkinsci-2Dusers_CAPiUgVerq2uUTBOzeY8Gwp2ebPRthjObtJ-5FA4M-253DeU1OZtRcA1w-2540mail.gmail.com-3Futm-5Fmedium-3Demail-26utm-5Fsource-3Dfooter=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=mXByn-k5ahdwHXfgIzt1kZhAXWCuXghYTJj4IHz05lc=2ysptL8ae42kRVa5benLWvcc11wYuWJ9PXganZfAz2Y=>
> .
>
>
> For more options, visit https://groups.google.com/d/optout
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=mXByn-k5ahdwHXfgIzt1kZhAXWCuXghYTJj4IHz05lc=N0RBCmmnoAD4p05B0Nzg5ZOj81T78N1yEGGjegZWksQ=>
> .
>
> --
> 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-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E2D8711CA0%40AMERMBX02.PERKINELMER.NET
> <https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E2D8711CA0%40AMERMBX02.PERKINELMER.NET?utm_medium=email_source=footer>
> .
>

RE: tidying up Ext-email output

2016-06-10 Thread Ginga, Dick

I can try that. the tests run for 45 minutes…

But it looks to me like $1 is eval’ing to ALL 3 lines instead of EACH line


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Slide
Sent: Friday, June 10, 2016 11:20 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: tidying up Ext-email output


Have you tried using  instead of \n?

On Fri, Jun 10, 2016, 08:18 Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
yes

From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of Slide
Sent: Friday, June 10, 2016 11:15 AM
To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Re: tidying up Ext-email output


Are you using html email?

On Fri, Jun 10, 2016, 08:01 Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
Hello all, just trying to create a “better” email response.

I have some custom written tests that produce lots of test output, but I only 
want the failures (FAIL:) in the email,

09:53:06 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST
…

09:54:09 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER
…

09:54:15 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT

so I use

${BUILD_LOG_REGEX, regex="(?i)( FAIL:.*)", substText="\n$1\n", 
showTruncatedLines=false, escapeHtml=true}

But I get this,

*** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT

I would like each of these failures to be on its own line. That is what I 
thought maybe the substText might do but apparently not.

Is there a way to do this?

Dick Ginga, Informatics R
PerkinElmer Inc. | For the Better
HUMAN HEALTH | ENVIRONMENTAL HEALTH
940 Winter Street, Waltham MA 02451

dick.gi...@perkinelmer.com<mailto:ed.cof...@perkinelmer.com>
Mobile – 508-847-1434
Office – 781-663-6947

--
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-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E2D8711C23%40AMERMBX02.PERKINELMER.NET<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_msgid_jenkinsci-2Dusers_6C6EE445A6F6CE4E8A0FFB51B071A4E2D8711C23-2540AMERMBX02.PERKINELMER.NET-3Futm-5Fmedium-3Demail-26utm-5Fsource-3Dfooter=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=mXByn-k5ahdwHXfgIzt1kZhAXWCuXghYTJj4IHz05lc=dglEPB15sKA_YOKPLxLdeKJ34vohwQQ8-KcqMNssCH0=>.
For more options, visit 
https://groups.google.com/d/optout<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=mXByn-k5ahdwHXfgIzt1kZhAXWCuXghYTJj4IHz05lc=N0RBCmmnoAD4p05B0Nzg5ZOj81T78N1yEGGjegZWksQ=>.
--
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-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVerq2uUTBOzeY8Gwp2ebPRthjObtJ_A4M%3DeU1OZtRcA1w%40mail.gmail.com<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_msgid_jenkinsci-2Dusers_CAPiUgVerq2uUTBOzeY8Gwp2ebPRthjObtJ-5FA4M-253DeU1OZtRcA1w-2540mail.gmail.com-3Futm-5Fmedium-3Demail-26utm-5Fsource-3Dfooter=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=mXByn-k5ahdwHXfgIzt1kZhAXWCuXghYTJj4IHz05lc=2ysptL8ae42kRVa5benLWvcc11wYuWJ9PXganZfAz2Y=>.

For more options, visit 
https://groups.google.com/d/optout<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=mXByn-k5ahdwHXfgIzt1kZhAXWCuXghYTJj4IHz05lc=N0RBCmmnoAD4p05B0Nzg5ZOj81T78N1yEGGjegZWksQ=>.
--
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-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E2D8711CA0%40AMERMBX02.PERKINELMER.NET<https://urldefense.proofpoint.

RE: tidying up Ext-email output

2016-06-10 Thread Ginga, Dick

yes

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Slide
Sent: Friday, June 10, 2016 11:15 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: tidying up Ext-email output


Are you using html email?

On Fri, Jun 10, 2016, 08:01 Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
Hello all, just trying to create a “better” email response.

I have some custom written tests that produce lots of test output, but I only 
want the failures (FAIL:) in the email,

09:53:06 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST
…

09:54:09 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER
…

09:54:15 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT

so I use

${BUILD_LOG_REGEX, regex="(?i)( FAIL:.*)", substText="\n$1\n", 
showTruncatedLines=false, escapeHtml=true}

But I get this,

*** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT

I would like each of these failures to be on its own line. That is what I 
thought maybe the substText might do but apparently not.

Is there a way to do this?

Dick Ginga, Informatics R
PerkinElmer Inc. | For the Better
HUMAN HEALTH | ENVIRONMENTAL HEALTH
940 Winter Street, Waltham MA 02451

dick.gi...@perkinelmer.com<mailto:ed.cof...@perkinelmer.com>
Mobile – 508-847-1434
Office – 781-663-6947

--
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-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E2D8711C23%40AMERMBX02.PERKINELMER.NET<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_msgid_jenkinsci-2Dusers_6C6EE445A6F6CE4E8A0FFB51B071A4E2D8711C23-2540AMERMBX02.PERKINELMER.NET-3Futm-5Fmedium-3Demail-26utm-5Fsource-3Dfooter=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=mXByn-k5ahdwHXfgIzt1kZhAXWCuXghYTJj4IHz05lc=dglEPB15sKA_YOKPLxLdeKJ34vohwQQ8-KcqMNssCH0=>.
For more options, visit 
https://groups.google.com/d/optout<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=mXByn-k5ahdwHXfgIzt1kZhAXWCuXghYTJj4IHz05lc=N0RBCmmnoAD4p05B0Nzg5ZOj81T78N1yEGGjegZWksQ=>.
--
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-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVerq2uUTBOzeY8Gwp2ebPRthjObtJ_A4M%3DeU1OZtRcA1w%40mail.gmail.com<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_msgid_jenkinsci-2Dusers_CAPiUgVerq2uUTBOzeY8Gwp2ebPRthjObtJ-5FA4M-253DeU1OZtRcA1w-2540mail.gmail.com-3Futm-5Fmedium-3Demail-26utm-5Fsource-3Dfooter=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=mXByn-k5ahdwHXfgIzt1kZhAXWCuXghYTJj4IHz05lc=2ysptL8ae42kRVa5benLWvcc11wYuWJ9PXganZfAz2Y=>.
For more options, visit 
https://groups.google.com/d/optout<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout=CwMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=mXByn-k5ahdwHXfgIzt1kZhAXWCuXghYTJj4IHz05lc=N0RBCmmnoAD4p05B0Nzg5ZOj81T78N1yEGGjegZWksQ=>.

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E2D8711CA0%40AMERMBX02.PERKINELMER.NET.
For more options, visit https://groups.google.com/d/optout.

Re: tidying up Ext-email output

2016-06-10 Thread Slide

Are you using html email?

On Fri, Jun 10, 2016, 08:01 Ginga, Dick  wrote:

> Hello all, just trying to create a “better” email response.
>
>
>
> I have some custom written tests that produce lots of test output, but I
> only want the failures (FAIL:) in the email,
>
>
>
> *09:53:06* *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST
>
> …
>
> *09:54:09* *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER
>
> …
>
> *09:54:15* *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT
>
>
>
> so I use
>
>
>
> ${BUILD_LOG_REGEX, regex="(?i)( FAIL:.*)", substText="\n$1\n",
> showTruncatedLines=false, escapeHtml=true}
>
>
>
> But I get this,
>
>
>
> *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST *** FAIL:
> LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER *** FAIL:
> LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT
>
>
>
> I would like each of these failures to be on its own line. That is what I
> thought maybe the substText might do but apparently not.
>
>
>
> Is there a way to do this?
>
>
>
> *Dick Ginga, Informatics R*
>
> *PerkinElmer Inc. *
> *| For the Better **HUMAN HEALTH **|* *ENVIRONMENTAL HEALTH*
> 940 Winter Street, Waltham MA 02451
>
>
>
> *dick.ginga**@perkinelmer.com *
>
> Mobile – 508-847-1434
>
> Office – 781-663-6947
>
>
>
> --
> 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-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E2D8711C23%40AMERMBX02.PERKINELMER.NET
> 
> .
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVerq2uUTBOzeY8Gwp2ebPRthjObtJ_A4M%3DeU1OZtRcA1w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

tidying up Ext-email output

2016-06-10 Thread Ginga, Dick

Hello all, just trying to create a "better" email response.

I have some custom written tests that produce lots of test output, but I only 
want the failures (FAIL:) in the email,

09:53:06 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST
...

09:54:09 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER
...

09:54:15 *** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT

so I use

${BUILD_LOG_REGEX, regex="(?i)( FAIL:.*)", substText="\n$1\n", 
showTruncatedLines=false, escapeHtml=true}

But I get this,

*** FAIL: LTU_FUNC_TEST.LIBCFSEARCH_HITCOUNTTEST *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_ATOMCENTER *** FAIL: 
LTU_FUNC_TEST.LIBCFSEARCH_STRINGRESULT

I would like each of these failures to be on its own line. That is what I 
thought maybe the substText might do but apparently not.

Is there a way to do this?

Dick Ginga, Informatics R
PerkinElmer Inc. | For the Better
HUMAN HEALTH | ENVIRONMENTAL HEALTH
940 Winter Street, Waltham MA 02451

dick.gi...@perkinelmer.com
Mobile - 508-847-1434
Office - 781-663-6947


-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E2D8711C23%40AMERMBX02.PERKINELMER.NET.
For more options, visit https://groups.google.com/d/optout.

RE: tidying up Ext-email output

Re: tidying up Ext-email output

RE: tidying up Ext-email output

Re: tidying up Ext-email output

RE: tidying up Ext-email output

Re: tidying up Ext-email output

RE: tidying up Ext-email output

RE: tidying up Ext-email output

Re: tidying up Ext-email output

RE: tidying up Ext-email output

Re: tidying up Ext-email output

RE: tidying up Ext-email output

RE: tidying up Ext-email output

Re: tidying up Ext-email output

RE: tidying up Ext-email output

RE: tidying up Ext-email output

Re: tidying up Ext-email output

tidying up Ext-email output

18 matches

Site Navigation

Mail list logo

Footer information