[
https://issues.apache.org/jira/browse/SQOOP-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693266#comment-14693266
]
Hudson commented on SQOOP-2425:
-------------------------------
SUCCESS: Integrated in Sqoop2 #866 (See
[https://builds.apache.org/job/Sqoop2/866/])
SQOOP-2425: Sqoop2: Precommit: Do not wipe out working directory on finish
(rzhou1:
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=e908d1597715c51f0e098e28ec4ff4b67e2ac9d9)
* dev-support/test-patch.py
> Sqoop2: Improve our pre-commit hook
> -----------------------------------
>
> Key: SQOOP-2425
> URL: https://issues.apache.org/jira/browse/SQOOP-2425
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.6
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
>
> I would like to propose several improvements to our pre-commit hook, so that
> it's even more useful then it's now :)
> Couple of ideas from top of my mind:
> * Order the actions that are performed. Right now the report always starts
> with ERRORS and I find it confusing. I would like to see order, something
> like "compilation success, unit test success, integration tests failed, ...).
> * Dependency checker. Detect if/when somebody adds a dependency and point it
> out (to verify that it's desired).
> * Save test log outputs, so that we can get to them. Their absence is making
> troubleshooting quite hard.
> * It would be great to add some additional static analysis - perhaps a
> checkstyle checker if we would have a rules to follow :)
> I'm sure that there are other ides, so please don't hesitate and comment what
> you would like to see!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)