mustafaiman commented on pull request #1069: URL: https://github.com/apache/hive/pull/1069#issuecomment-640740432
> another approach which could be considered: publish the findbugs report in the build - I think it will be there even if the build fails > some of this might work: > https://www.jenkins.io/doc/pipeline/steps/htmlpublisher/ > https://www.jenkins.io/blog/2017/02/10/declarative-html-publisher/ > I think it could be published in a "finally" block somewhere around compile... If we are aiming to enforce clean findbugs in every pull request, I dont see much benefit in having a findbugs report. It is going to be empty all the time apart from the bugs you might introduce in your patch. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
