[JIRA] (JENKINS-42755) BFA fails to catch pipeline related exceptions

sorin.sbarnea@gmail.com (JIRA)

unread,

Mar 14, 2017, 10:16:01 AM3/14/17

to jenkinsc...@googlegroups.com

Sorin Sbarnea created an issue

Jenkins /

JENKINS-42755

BFA fails to catch pipeline related exceptions

Issue Type:	Improvement
Assignee:	Tomas Westling
Components:	build-failure-analyzer-plugin
Created:	2017/Mar/14 2:15 PM
Priority:	Critical
Reporter:	Sorin Sbarnea

Here is an interesting bug related to BFA and pipelines.

When the job runs BFA fails to spot the exception as this exceptions seems to reach stdout after BFA runs.

If I force the BFA to rescan the builds it will spot it.

I find this behaviour confusing, can we fix it?

 
                                                                [Pipeline] }
[Pipeline] // timestamps
[Pipeline] End of Pipeline
[BFA] Scanning build for known causes...
[BFA] No failure causes found
[BFA] Done. 0s
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object (org.jenkinsci.plugins.workflow.cps.CpsClosure2 scm java.util.LinkedHashMap)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectMethod(StaticWhitelist.java:183)
	at 
 
                                                            

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

jvallon1@bloomberg.net (JIRA)

unread,

Dec 9, 2018, 3:50:03 PM12/9/18

to jenkinsc...@googlegroups.com

Justin Vallon commented on

JENKINS-42755

Re: BFA fails to catch pipeline related exceptions

I had the same trouble, and am also using the "timestamps" feature. When timestamps is active, it prefixes every line of output with a date+time; it seems BFA wants that to match as well. I added '^.*' to my rule, and now it matches the lines in the "Failure Cause Editor" and it was able to find "Identified Problems" in the build page.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

will@nowhereetc.com (JIRA)

unread,

Dec 14, 2018, 1:49:02 PM12/14/18

to jenkinsc...@googlegroups.com

Will Freeman commented on

JENKINS-42755

Re: BFA fails to catch pipeline related exceptions

The timestamps thing I expect, however, we experience the exact same issue as the OP. It appears anything output from stderr is not processed by BFA on the build run, but only after in the subsequent scan.