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
<https://lh3.googleusercontent.com/-ReK1VVomRIw/WYQ4inmKK7I/AAAAAAAABQo/NHWQB6SvOQMMbLWI17QyovpWd_RHBk-GwCLcBGAs/s1600/Screenshot%2Bfrom%2B2017-08-04%2B11-03-37.png> <https://lh3.googleusercontent.com/-D_yp4pOmcZY/WYQ4tyvbwVI/AAAAAAAABQs/yzWZ-oujqZ0mqFlr1z1PAq6bkK14prukACLcBGAs/s1600/Screenshot%2Bfrom%2B2017-08-04%2B11-04-36.png> <https://lh3.googleusercontent.com/-3noV02Rdl58/WYQ5ATBvUkI/AAAAAAAABQw/fgvBMSZ1QiopbkUfk6fD7NPKzE0N3luJwCLcBGAs/s1600/Screenshot%2Bfrom%2B2017-08-04%2B11-05-38.png> /B On Thursday, July 20, 2017 at 9:08:26 AM UTC+2, Shiran wrote: > > 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! :) > > On Wednesday, July 19, 2017 at 4:38:24 PM UTC+3, Eric Pyle wrote: >> >> 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 >> >> On 7/19/2017 2:48 AM, Shiran wrote: >> >> 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!* >> -- >> 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 >> >> <https://groups.google.com/d/msgid/jenkinsci-users/f71e269b-1929-46ee-80a5-874f8e69b72c%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> Eric Pyle >> Siemens PLM Software >> Lebanon, NH >> +1 603-277-3060eric...@siemens.comhttp://www.siemens.com/plm >> >> -- 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/e7c9ce4a-e8b8-417e-9f83-6436aa3f50b2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
