To use the EC2 service with Buildbot, there needs to be some way for Buildbot to dynamically generate a list of build slaves. These build slaves (or just slaves) are hosted as a virtual machine on the EC2 service.
Probably This will work by extending the best way BuildSlave class to do this is add in some new functionality for starting a new EC2 instance. So, every time you add a new slave to extend the BuildSlave classslave list, another instance will be spwaned, and make so that you can spawn as many instances as you think you will need to complete a new class called EC2BuildSlavebuild.
Theres a couple good reasons for extending this class. One big one I can think about is that the This new BuildSlave class will have start a different way of disconnectingnew instance, where it which will have then proceed to send a command to the EC2 service connection information of the master to shut the new instance down (thats if it. How exactly, I's m not being used by some other build master)exactly sure, because it takes a minute for the virtual instance to start up.
Making this new slave class will also be a much neater way to implement this new functionality, instead The rest basically takes care of having functions just randomly and haphazardly placed all overitself.
Lots more research and code reviewing Still have to think about how to turn the new EC2 instances off after the build is still on the horizon for this project, but this release should be ready in a months timedone.
----
