Multiline regex not working in Build Failure Analyzer Plugin

561 views
Skip to first unread message

Shiran

unread,
Jul 19, 2017, 2:54:51 AM7/19/17
to Jenkins Users

Hi, 

I've been struggling for days in making the multiline build log indication work.

I couldn’t find any example in the net, I had it working in a Groovy console but not in Jenkins.

 

This is the Jenkins log.  I want to detect the yellow part – if I find these two yellow strings are the indication of the failure:

22:14:36 2017-07-10 22:14:36   Test     INFO:  busy: -E- T:78008253   

22:14:36 2017-07-10 22:14:36   Test     INFO:  busy: Segmentation fault

22:14:36 2017-07-10 22:14:36   Test     INFO:  busy: Error! failed to run driver tests

22:14:36 2017-07-10 22:14:36   Test     INFO:  busy: /opt/cve_driver_test

22:14:36 2017-07-10 22:14:36   Test     INFO:  busy: Return1Code

 

I tried to find this pattern in a groovy console and succeeded:

def pattern "(?s)Segmentation fault(.*)busy: Error! failed to run driver tests"            
def example1 text.find(pattern//=> found!


How do I make it work Jenkins?

Thanks!

Eric Pyle

unread,
Jul 19, 2017, 9:38:24 AM7/19/17
to jenkins...@googlegroups.com
I think the pattern has to match full lines, so you would need:

".*Segmentation fault.*busy: Error! failed to run driver tests"

in the multiline regex definition box in BFA. No need to put .* in parentheses.

Eric
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f71e269b-1929-46ee-80a5-874f8e69b72c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
Eric Pyle
Siemens PLM Software
Lebanon, NH
+1 603-277-3060
eric...@siemens.com
http://www.siemens.com/plm

Shiran

unread,
Jul 20, 2017, 3:08:26 AM7/20/17
to Jenkins Users
Eric thank you for your help.
Yet, this is still not working for me.

Could you give me an example of a Jenkins log of yours and a multiline in BFA that actually work? (maybe you could attach a screen shot of the BFA page in Jenkins.)

Thanks! :)

Robert Sandell

unread,
Aug 4, 2017, 5:07:40 AM8/4/17
to Jenkins Users
Both Shiran's and Eric's patterns work for me, but Shiran's is a bit more accurate in finding the offending start line when navigating the found indication from the build page


/B

Shiran

unread,
Aug 6, 2017, 2:59:20 AM8/6/17
to Jenkins Users
Hi Robert,
Thank you for your help.
The regex you suggested, (?s)Segmentation fault(.*)busy: Error! failed to run driver tests,  is not working for me.
Maybe it has something to do with the plugin or/and Jenkins version?

Thanks!

Victor Martinez

unread,
Aug 6, 2017, 12:08:17 PM8/6/17
to Jenkins Users
I was able to test it and it works like a charm with the below versions:
- BFA: 1.19.0
- Jenkins 2.60.2

Cheers 
Reply all
Reply to author
Forward
0 new messages