[
https://issues.apache.org/jira/browse/HIVE-16749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034917#comment-16034917
]
Zoltan Haindrich commented on HIVE-16749:
-----------------------------------------
I've attached the patch..but I've set up a build on the docker hub - it will
start building the findbugs enabled image in a few minutes...it will be
available in about an hour?....
so the following should launch a yetus validation of a patch:
{code}
docker run --rm -it -v ~/.m2/settings.xml:/root/.m2/settings.xml
kgyrtkirk/hive_yetus /run_yetus.bash
"https://issues.apache.org/jira/secure/attachment/12842555/HIVE-15053.2.patch";
{code}
The other parts of {{dev-support/test-patch2.sh}} are only there to support
"local" patchfiles.
[~pvary] I think this way we have finer gained control over the whole
environment...and over the yetus sources as well - what do you think?
> Run YETUS in Docker container
> -----------------------------
>
> Key: HIVE-16749
> URL: https://issues.apache.org/jira/browse/HIVE-16749
> Project: Hive
> Issue Type: Sub-task
> Reporter: Peter Vary
> Assignee: Zoltan Haindrich
> Attachments: HIVE-16749.1.patch
>
>
> Think about the pros and cons of running YETUS in a docker container:
> - Resources
> - Usage complexity
> - Yetus version changes
> - Findbugs
> - etc.
> If worthwhile run YETUS in a docker container
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
