Hello everyone, Chop uses AWS EC2 instances to run both chop webapp and runners (instances which run tests). We tried hard to make everything as easy as possible in Chop and currently we are providing an AMI for runners on which Oracle Java is already installed. However it is not legal to distribute Oracle Java in such a public platform, so we had a discussion in our chop team. Here are the different options that came out from that discussion, please feel free to comment.
(1) We may provide a public AMI with OpenJDK, actually we already created one for runner instances. But, although our runner core runs properly with OpenJDK, code that's going to be Chop tested may have problems with it, so it's at users risk to go this way. (2) We may ask user to provide a link on chop web UI to download oracle tar ball if he/she wants Oracle JDK on runner instances. After we download tar ball using that link, we will install Oracle Java to runner instances. This way user will have already dealt with license approval process. (User may provide S3 bucket address for this) (3) We may ask user to approve the Oracle license agreement with a popup window while he/she configures runner instances on web UI, then we can download tar ball from Oracle's website using wget as explained in the below link and install it on runner instances. http://stackoverflow.com/questions/10268583/how-to-automate-download-and-installation-of-java-jdk-on-linux . (4) Option #2 and #3 may take a lot time, since on each runner instance creation, it'll download the tar ball either from link that user provide or Oracle's website, extract it, configure and install it. Therefore we came up with option #4 : Chop web UI may have a separate tool, or an option on UI, so that if the user wants his private AMI with Oracle JDK installed inside he can again accept the license agreement, then we open up an EC2 instance, download & install the Oracle JDK than make that instance a private AMI for the user, and put its AMI id in image ID section in the UI. This way, users can have their private AMIs with just a couple of clicks and the setup time will not be affected. Among these options, #1 is ready to use and other options are possible candidates to be implemented if we agree on them. Out of these options, of course user can create its own private AMI, and provide its AMI id to chop web UI to start using Chop. Regards, Salih
