hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11944) add option to test-patch to avoid relocating patch process directory
Date Mon, 11 May 2015 19:38:02 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-11944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538506#comment-14538506

Sean Busbey commented on HADOOP-11944:

Right, when using test-patch to handle another project, I've been going with a workspace that
looks like this:

     |--- testframework (hadoop git checkout)
     |--- component (project-under-test git checkout)
     \--- patchprocess (scratch dir cleaned by jenkins)

Then I invoke test-patch within testframework while giving a BASEDIR that's the component
to test. This lets Jenkins handle the two git repos cleanly and archive things out of patchprocess.

> add option to test-patch to avoid relocating patch process directory
> --------------------------------------------------------------------
>                 Key: HADOOP-11944
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11944
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Minor
>         Attachments: HADOOP-11944.1.patch
> When we have a jenkins setup that places the patch process in a defined location under
WORKPLACE, there's no need to have patch process relocate it. Add a flag to leave it as is.

This message was sent by Atlassian JIRA

View raw message