[
https://issues.apache.org/jira/browse/HADOOP-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated HADOOP-11933:
--------------------------------------
Attachment: HADOOP-11933.02.patch
-02:
* rebased
* Work around the incredibly stupid $USER setting on the jenkins account
* Remove sudo since jenkins as the ability to execute it without it
* re-arrange the directories a bit so we have a Well Known Location in the
container
* Try to genericize it a bit more, including passing in the project name
* Add an entry to the table to show when we are running in a container for the
test run
* Pass in the build url on the command line
* clean up all the new shellcheck errors generated by the newer shellcheck
version this patch uses
* --docker => turn on docker support
* --dockermode => running in a docker container
* re-arrange the patch dir bits so we can test for relational location first
* move close_jira_footer to open_jira_footer so that those entries are filled
in first
*NOTE*: The HADOOP precommit job has been modified to have the --docker flag
for test-patch.sh to enable testing of this patch in a docker container. :)
> 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
>
>
> 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)
