I, too, have had trouble passing the CI quality gate checks in plugins with existing SpotBugs violations. In my opinion, it is better to suppress SpotBugs violations at the Maven build level (or with @SuppressFBWarnings annotations) than at the CI level by comparing against a baseline, since that way failures are deterministic and the status of the local build is identical to the status of the CI build. In core, core components, and several plugins, I have added Spotbugs exclusions to an XML file to ensure that existing violations do not fail the build while new violations do.
-- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjoVAsHcN73%2B4vrhq_YRHLemi1J19sfvhYO8juHN2h0jGw%40mail.gmail.com.
