[
https://issues.apache.org/jira/browse/HIVE-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13701639#comment-13701639
]
Brock Noland commented on HIVE-4739:
------------------------------------
[~appodictic]
OK I think this is ready. To summarize
* A dedicated ec2 medium instance runs a webservice which is used to kick of
the build
* The build starts up 8 ec2 spot instances and then runs the build (these stick
around for a half hour waiting for another build)
* It seems to work well, see more details here:
https://issues.apache.org/jira/browse/HIVE-4675?focusedCommentId=13701636&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13701636
* This is extremely cheap and handling multiple ec2 keys would be complex.
Therefore let's just charge this to my employer for now and then later we can
add multiple ec2 key support to ptest2.
* Once HIVE-4815 is resolved I can create the automated "patch available"
testing
I am ready to create accounts for hive committers that are interested. In order
to protect the ec2 key, the account will not have full sudo access. However,
the account will be able to:
* Stop/Start/Restart the ptest2 service
* Push the latest changes to ptest2 from trunk
* Look at all logs
How does this sound?
> Create public parallel test environment
> ---------------------------------------
>
> Key: HIVE-4739
> URL: https://issues.apache.org/jira/browse/HIVE-4739
> Project: Hive
> Issue Type: Improvement
> Reporter: Brock Noland
> Assignee: Brock Noland
>
> See discussion here
> http://mail-archives.apache.org/mod_mbox/hive-dev/201306.mbox/%3CCAENxBwx%3Dc4VFLhR1zXZ3uWbP2BUFZc%2BZuiqF4SZY5zUZ9%2BUcxQ%40mail.gmail.com%3E
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
