Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-42755

BFA fails to catch pipeline related exceptions

    XMLWordPrintable

    Details

    • Similar Issues:
    • Released As:
      1.23.0-beta-1

      Description

      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 
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              t_westling Tomas Westling
              Reporter:
              ssbarnea Sorin Sbarnea
              Votes:
              12 Vote for this issue
              Watchers:
              13 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: