The main goal of So this release iteration is to make basically about getting this project as useable and accessible to as many people as possibleinto the “publically useable” stage. Right now, the EC2 instance that is it’s fairly easy to set up will only work for connecting to one server, because the build masters IP address is hard coded into the instance. There is a way of sending the build masters IP address these modifications to the instance at run time, so the instance can use the EC2 instances in any Buildbot build masters IP address in the startup scriptproject.

I would also like To use, you need to get a script written for people have Buildbot installed already. Then, you need to use in their startup to allow download the BOTO python library from Google, and place the creation of custom EC2 instances boto folder from that will have the same Buildbot functionalityzip file into your build-master directory. Then, you need to extract this patch into your build-master directory. Thats it for system prep.

AlsoThen, can't forget you need to go to AWS.AMAZON.COM and sign up for an account. When you do that, you will need to get your Public Key, and Secret Key to paste into your build-master’s master.cfg file. In your build-masters master.cfg file, where you would normally specify your list of BuildSlaves, you will be replacing BuildSlave with EC2BuildSlave. This custom class is what allows Buildbot to start EC2 instances and create slaves to use on them. You need to specify a few extra variables in the slave configuration. By default, you need to specify:  * Bot Name * Bot Password * Public Key * Private Key * [IP Address of Build-Master:Port] [Bot Name] [Bot Password] By supplying the build-master’s IP address to the EC2 slave, you are allowing the build-slave on the whole point EC2 instance to be pointed at your machine. If you have a DNS, then that will work in this projectplace as well. Building Mozilla on  There is a generic Amazon EC2 Using Buildbotinstance (also called an AMI) created that is set by default in the EC2BuildSlave class. Builds work nowHowever, if you desire, so I don't see you may also insert a reason why I wouldn't be able custom AMI instance ID to the EC2BuildSlave and have it start up your own AMI. See the custom startup script, in the 0.3 deliverable zip, to use EC2 insert into your instance to have your build mozilla, but I guess we'll see-slave created at run-time.