[
https://issues.apache.org/jira/browse/HADOOP-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540342#comment-14540342
]
Allen Wittenauer commented on HADOOP-11933:
-------------------------------------------
bq. what does one need to check? I guess a login on the jenkins boxes?
Either that or run it locally. But at this point, I've determined that no one
is taking care to clean up images on the jenkins hosts themselves. A lot of
that is Docker's image management, because it certainly doesn't help. The new
code is waaaaaay better about cleaning out dead/broken build bits. I'm not
that worried about it anymore.
I'm pretty much ready to commit. I don't think there will be any fallout, but
any time you mess with this stuff, there always is... lol
> 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, HADOOP-11933.01.patch,
> HADOOP-11933.02.patch, HADOOP-11933.03.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)
