[
https://issues.apache.org/jira/browse/HADOOP-12146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606632#comment-14606632
]
Allen Wittenauer edited comment on HADOOP-12146 at 6/29/15 11:13 PM:
---------------------------------------------------------------------
IMO, per-run is going to be expensive and slow. Per-project doesn't protect
projects against themselves. I think per-project, per-branch is probably the
correct mix. Also, I think this mode should run in effectively three ways:
* no override
* custom directory specified by the user
* some default directory path structure (e.g.,
$\{HOME\}/test-patch-maven/$\{project\}/$\{branch\}
In the case of the latter, we'll need to build some self-cleaning code similar
to the things we're doing for docker in general.
was (Author: aw):
IMO, per-run is going to be expensive and slow. Per-project doesn't protect
projects against themselves. I think per-project, per-branch is probably the
correct mix. Also, I think this mode should run in effectively three ways:
* no override
* custom directory specified by the user
* some default directory path structure (e.g.,
${HOME}/test-patch-maven/${project}/${branch}
In the case of the latter, we'll need to build some self-cleaning code similar
to the things we're doing for docker in general.
> dockermode should support custom maven repos
> --------------------------------------------
>
> Key: HADOOP-12146
> URL: https://issues.apache.org/jira/browse/HADOOP-12146
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: yetus
> Affects Versions: HADOOP-12111
> Reporter: Allen Wittenauer
>
> On busy jenkins servers, it only takes one bad apple doing a
> dependency:purge-local-repository to wreak havoc on other projects. In order
> to protect against this, test-patch should have some way to overlay the .m2
> directory with something that is (minimally) per-project and maximally per
> run.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
