[
https://issues.apache.org/jira/browse/HIVE-16749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066352#comment-16066352
]
Peter Vary commented on HIVE-16749:
-----------------------------------
Running Yetus takes some time, and I think we do not want to make the
pre-commit test take any longer. That is why I think the best solution would be
to run the compile needed for the ptest and start the ptest runs, and only
after we started the ptest runs should we start to run Yetus.
This means that Yetus will compile the source twice anyway, so we could go
ahead with the dockerized runs if it helps us with cleaner code.
What do you think [~kgyrtkirk], [~spena]?
> 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.4.14#64029)
