[
https://issues.apache.org/jira/browse/HIVE-16749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025879#comment-16025879
]
Zoltan Haindrich commented on HIVE-16749:
-----------------------------------------
[~pvary] I've been playing with this a bit...I think this way it will be
probably more "safer" to execute this check - since I don't want anything to
change anything in my workspace....
and the way this applies the fixes....makes it unneccessary the 'wrapper'
shellscript
https://github.com/apache/hive/compare/master...kgyrtkirk:yetus-docker
currently it requires that the dockerd to run on the same host the developer is
using (to pass the patch file) - although I think it would be better to lift
this restriction; it works for me now...
> 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: Peter Vary
>
> 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)
