[
https://issues.apache.org/jira/browse/HADOOP-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533205#comment-14533205
]
Allen Wittenauer edited comment on HADOOP-11933 at 5/7/15 6:59 PM:
-------------------------------------------------------------------
[~owen.omalley] suggested using COW to handle the .m2 dir. Doing some digging
seems to indicate this is a much desired feature of docker, but isn't really
well implemented outside of the image file. (... and building an image with
all of .m2 doesn't sound like a good idea. lol)
Other suggestions are to use overlayfs from within the client so I might try
that.
was (Author: aw):
[~owen.omalley] suggested using COW to handle the .m2 dir. Doing some digging
seems to indicate this is a much desired feature of docker, but isn't really
well implemented outside of the image file. (... and building an image with
all of .m2 doesn't sound like a good idea. lol)
Other suggestions are to use overlayfs so I might try that.
> run test-patch.sh in a docker container under Jenkins
> -----------------------------------------------------
>
> Key: HADOOP-11933
> URL: https://issues.apache.org/jira/browse/HADOOP-11933
> Project: Hadoop Common
> Issue Type: Test
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Attachments: HADOOP-11933.00.patch
>
>
> because of how hard it is to control the content of the Jenkins environment,
> it would be beneficial to run it in a docker container so that we can have
> tight control of the environment
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
