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] [Created] (SQOOP-1832) Sqoop2: Enforce that integration test working directory is always in target/ directory
Date Wed, 03 Dec 2014 02:13:12 GMT
Jarek Jarcec Cecho created SQOOP-1832:
-----------------------------------------

             Summary: Sqoop2: Enforce that integration test working directory is always in
target/ directory
                 Key: SQOOP-1832
                 URL: https://issues.apache.org/jira/browse/SQOOP-1832
             Project: Sqoop
          Issue Type: Bug
    Affects Versions: 1.99.4
            Reporter: Jarek Jarcec Cecho
            Assignee: Jarek Jarcec Cecho
             Fix For: 1.99.5


I've noticed that on certain executions (for example {{mvn integration-test -pl test}} we're
using OS's temp directory ({{/tmp}} on linux, {{/var/folders/bf/...}} on mac OS X) instead
of the configured {{target/}} directory.

This is relatively small issue, but I would like to fix it because:
* The tmp directory is not discoverable in Jenkins, so we can't get to all logs without SSH
to target Jenkins slave
* {{mvn clean}} won't clean up those files
* The directory can get reused if one runs the tests twice on single machine (from two different
directories)

I believe that the problem is that we're defining the [test's temporary directory|https://github.com/apache/sqoop/blob/sqoop2/test/pom.xml#L157]
in the pom file using environmental variable {{sqoop.integration.tmpdir}} conditionally only
in some profiles. We should simply set it in all profiles.



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

Mime
View raw message