[
https://issues.apache.org/jira/browse/HIVE-23629?focusedWorklogId=442302&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-442302
]
ASF GitHub Bot logged work on HIVE-23629:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Jun/20 19:17
Start Date: 06/Jun/20 19:17
Worklog Time Spent: 10m
Work Description: pgaref commented on pull request #1069:
URL: https://github.com/apache/hive/pull/1069#issuecomment-640106037
Seems to be doing the job, check here:
http://130.211.9.232/blue/organizations/jenkins/panos-precommit/detail/panos-precommit/3/pipeline
I was just wondering if we should push the results back to JIRA in the form
of a report or something..
----------------------------------------------------------------
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]
Issue Time Tracking
-------------------
Worklog Id: (was: 442302)
Time Spent: 20m (was: 10m)
> Enforce clean findbugs in PRs
> -----------------------------
>
> Key: HIVE-23629
> URL: https://issues.apache.org/jira/browse/HIVE-23629
> Project: Hive
> Issue Type: Sub-task
> Reporter: Mustafa Iman
> Assignee: Mustafa Iman
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We should start enforcing clean findbugs reports as soon as we fix a module.
> Otherwise, it will continue collecting findbugs errors. We can add a stage to
> Jenkins pipeline to enforce findbugs and possibly other checks. It will
> selectively run findbugs for specified sub modules. Eventually we can get rid
> of the list and enable findbugs for the whole project.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
