Improve error handling in PipelineVulnerabilitiesFinder#execute

In PipelineVulnerabilitiesFinder#execute we have rescue NoMethodError => _ # propagate error for CompareReportsBaseService (code) that handles nils, but we should improve this design.

The following discussions from !15531 (merged) should be addressed:

  • @godfat started a discussion: (+3 comments)

    This is actually the same as before. Without mentioning anything, it's StandardError. Could we be more specific? A StandardError can be anything.

Edited Aug 29, 2019 by rossfuhrman
Assignee Loading
Time tracking Loading