Hey Thomas,
Yes I can find string “Can not access” in build log, for this particular log
there is no “full log” link it is just one page smaller log.
Thanks,
Jhoom
-----Original Message-----
From: Westling, Tomas <tomas.westl...@sonymobile.com>
To: 'jhoomshar...@netscape.net' <jhoomshar...@netscape.net>; jenkinsci-users
<jenkinsci-users@googlegroups.com>; Sandell, Robert
<robert.sand...@sonymobile.com>
Sent: Wed, Jan 30, 2013 11:50 am
Subject: RE: Build failure analyzer pattern issue
Can you find the text in the log if you do a text search?
Is the log longer than what can fit initially when you show the console?
I.e. do you need to press the “full log” link to show the whole log?
We do have an issue where the links and red marking has a problem with logs
where only parts of it is shown and “full log” link exists. We are working on a
bug fix
for this and should be done pretty soon.
Br Tomas Westling,
Sony Mobile Communications
From: jhoomshar...@netscape.net [mailto:jhoomshar...@netscape.net]
Sent: den 29 januari 2013 19:06
To: jenkinsci-users@googlegroups.com; Sandell, Robert; Westling, Tomas
Subject: Re: Build failure analyzer pattern issue
Yeah thanks Robert for timely response.
It looks like Build Failure Analyzer behavior is not consistent, I have a
pattern ".*Can not access.*", plugin shows me it has "Identified problems" with
"Indication 1" in Unstable build but when I navigate my unstable build log it
does not highlight the problem with red mark nothing is there in logs from
Build Failure Analyzer plugin.
If I have to investigate on this issue what all should I check in Jenkins log,
so that will get a clear picture on where things are going wrong.
-----Original Message-----
From: Sandell, Robert <robert.sand...@sonymobile.com>
To: 'jhoomshar...@netscape.net' <jhoomshar...@netscape.net>; jenkinsci-users
<jenkinsci-users@googlegroups.com>; Westling, Tomas
<tomas.westl...@sonymobile.com>
Sent: Thu, Jan 24, 2013 9:46 pm
Subject: RE: Build failure analyzer pattern issue
Your regexp is set to find the text “Failures:” followed by at least one digit,
which it does (Failures: 0)
You would need something like
.*Failures: [1-9]\d*.*
To catch any digit combination except for “Failures: 0”
Robert Sandell
Software Tools Engineer - SW Environment and Product Configuration
Sony Mobile Communications
From: jhoomshar...@netscape.net [mailto:jhoomshar...@netscape.net]
Sent: den 24 januari 2013 15:21
To: jenkinsci-users@googlegroups.com; Westling, Tomas
Cc: Sandell, Robert
Subject: Re: Build failure analyzer pattern issue
Looks like there is some issue with pattern matching here, I have unit test
failure with “Build log indication” as follows:
“.*Failures: \d+.*” and “.*Errors: \d+.*”
Above pattern is not matched properly for build failures it is matching
following line:
[junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 1.058 sec (this
line does not contain any Failure or Error)
Another example is it matching successful “rsync” command in build log, which
has nothing to do with unit test failure and no pattern “Failure” or “Error”
matches to this line, this is strange.
I have no idea what and where things are going wrong, either pattern is not
correct or something to do with Build Failure Analyzer.
Any help in this regard.
Thanks,
Jhoom
-----Original Message-----
From: Tomas Westling <tomas.westl...@sonymobile.com>
To: jenkinsci-dev <jenkinsci-...@googlegroups.com>
Cc: jenkinsci-users <jenkinsci-users@googlegroups.com>; robert.sandell
<robert.sand...@sonymobile.com>; tomas.westling
<tomas.westl...@sonymobile.com>; jhoomsharabi <jhoomshar...@netscape.net>
Sent: Wed, Jan 9, 2013 12:03 pm
Subject: Re: Build failure analyzer pattern issue
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
On Tuesday, January 8, 2013 5:48:34 PM UTC+1, jhooms...@netscape.net wrote:
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
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
