Re: Build failure analyzer pattern issue

526 views
Skip to first unread message

jhooms...@netscape.net

unread,
Jan 8, 2013, 11:48:34 AM1/8/13
to jenkins...@googlegroups.com, jenkin...@googlegroups.com, robert....@sonymobile.com, tomas.w...@sonymobile.com
Hi,
I am trying to implement “build failure analyzer” plugin to my Jenkins projects but it’s not working for me, say I am getting build issue like this:
 
Reason: Cannot find parent: net.java:jvnet-parent for project: com.sun.jersey:jersey-project:pom:1.9.1 for project com.sun.jersey:jersey-project:pom:1.9.1
 
I am trying to match pattern “Cannot find parent”, but looks like build failure analyzer is not respecting this pattern or maybe I am giving wrong pattern match. I am getting following output from build failure anyalyzer:
 
Identified problems
               No identified problems
               No problems were identified. If you know why this problem occurred, please add a suitable Cause for it.
 
Can anyone help me out in this, it will be great help.
 
Thanks,
Jhoom

Tomas Westling

unread,
Jan 9, 2013, 1:33:18 AM1/9/13
to jenkin...@googlegroups.com, jenkins...@googlegroups.com, robert....@sonymobile.com, tomas.w...@sonymobile.com, jhooms...@netscape.net
Hello Jhoom,

the build failure analyzer uses Matcher.matches() to see if a regular expression matches its target.
The reason for this is performance, we used find() earlier but we saw very long scan times.
This means that you have to match the entire line, not just something that exists in the line, e.g.
.*Cannot find parent.*

This would match for "Cannot find parent" anywhere in a line.

Br Tomas Westling
Sony Mobile Communications AB

Sandell, Robert

unread,
Jan 9, 2013, 5:06:10 AM1/9/13
to jhooms...@netscape.net, jenkins...@googlegroups.com, jenkin...@googlegroups.com, Westling, Tomas

Hi,

For performance reasons the BFA uses full match per line.

So try “Cannot find parent.*

And see if that works.

 

 

Robert Sandell

Software Tools Engineer - SW Environment and Product Configuration

Sony Mobile Communications

jhooms...@netscape.net

unread,
Jan 10, 2013, 12:06:26 PM1/10/13
to tomas.w...@sonymobile.com, jenkin...@googlegroups.com, jenkins...@googlegroups.com, robert....@sonymobile.com
Thanks Westling it's working now.



 
-----Original Message-----
From: Tomas Westling <tomas.w...@sonymobile.com>
To: jenkinsci-dev <jenkin...@googlegroups.com>
Cc: jenkinsci-users <jenkins...@googlegroups.com>; robert.sandell <robert....@sonymobile.com>; tomas.westling <tomas.w...@sonymobile.com>; jhoomsharabi <jhooms...@netscape.net>
Sent: Wed, Jan 9, 2013 12:03 pm
Subject: Re: Build failure analyzer pattern issue

jhooms...@netscape.net

unread,
Jan 31, 2013, 5:22:45 AM1/31/13
to jenkins...@googlegroups.com, Tomas.W...@sonymobile.com, Robert....@sonymobile.com, jenkin...@googlegroups.com
Hi,
First I have no idea why my unstable or failed builds are generating double logs, after a bit of investigation found that Build Failure Analyzer plugin is doing the trick so went to system configuration page (Manage Jenkins -> Configure System) and tried to uncheck “Convert knowledge base” and “Send notifications to Gerrit-Trigger-plugin”, once uncheck I saved my Configure System page but to my surprise what I found that after saving configuration the uncheck “Convert knowledge base” again got enabled.
Any idea what’s going wrong here, for time being I disabled my “Build failure Analyzer” plugin to make the logs stable.
Attaching screen shot for your reference.
 
Thanks,
Jhoom
Build_Failure_Analyzer_3.jpg

jhooms...@netscape.net

unread,
Jan 31, 2013, 12:26:41 PM1/31/13
to jenkin...@googlegroups.com, jenkins...@googlegroups.com, Tomas.W...@sonymobile.com, Robert....@sonymobile.com
Build_Failure_Analyzer_3.jpg
Reply all
Reply to author
Forward
0 new messages