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-11933) run test-patch.sh in a docker container under Jenkins
Date Wed, 20 May 2015 15:21:02 GMT

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

Sean Busbey commented on HADOOP-11933:
--------------------------------------

{code}
+function cleanup_apache_jenkins_docker
+{
+  # On Jenkins, do some cleanup of old stuff since
+  # no body else seems to be
+
{code}

{code}
+  # make a base image, if it isn't available
+  dockercmd build -t "${baseimagename}" "${BINDIR}"
+
+  # using the base image, make one that is patch specific
{code}

Can we add some timing in here so we know how much time patch-tester is spending on docker
maintenance?

> 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, HADOOP-11933.04.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)

Mime
View raw message