sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-1833) Sqoop2: Add elapsed time information to pre-commit hook
Date Wed, 03 Dec 2014 02:57:13 GMT

     [ https://issues.apache.org/jira/browse/SQOOP-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jarek Jarcec Cecho updated SQOOP-1833:
--------------------------------------
    Attachment: SQOOP-1833.patch

> Sqoop2: Add elapsed time information to pre-commit hook
> -------------------------------------------------------
>
>                 Key: SQOOP-1833
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1833
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.99.4
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>            Priority: Minor
>             Fix For: 1.99.5
>
>         Attachments: SQOOP-1833.patch
>
>
> As of SQOOP-1777 we're running integration tests as part of the pre-commit hook and as
we will add more and more tests, I think that it would be useful to also have an idea how
long the pre-commit hook needs to execute.
> Whereas this information is available on Jenkins, I'm assuming that people won't be checking
it there at all and hence I would like to build in such capability directly into the hook
and simply print out in each Sqoop QA bot comment how long it took to test given patch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message