BFA fails to catch pipeline related exceptions

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • 1.23.0-beta-1

      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

            Assignee:
            Tomas Westling
            Reporter:
            Sorin Sbarnea
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: