I agree, I would much, much rather be using ec2 nodes. However, ec2 doesn't support what is, unfortunately, a primary platform for us and thats OSX. For whatever, reason there are a fair number of OSX users for both erlang in general and erlware. Otherwise, this is absolutely the way I would go.
On Thu, Jul 14, 2011 at 11:41 AM, Salomon Elizondo <[email protected]> wrote: > that still holds true for ec2 nodes, schedule build process to spin up > your master/slave nodes publish results to micro node and hibernate > the rest of the nodes. > > On Thu, Jul 14, 2011 at 10:16 AM, Eric Merritt <[email protected]> wrote: >> ha! >> >> I am something of an idiot. The biggest problem that I had was that a >> dedicated host with enough power and memory to handle virtual machines >> the virtual machines required is pretty expensive, as is colocation. >> However, I just realized that I don't need any of that!! A build >> server only needs to be mostly connected, not connected full time and >> as long as it can publish its results somewhere, it doesn't even need >> to be generally available on a static ip. So I can buy a box with a >> decent amount of memory, and a decent processer, stick it in my house >> (or some place like that) as long as its mostly connected it should >> work and be a fairly inexpensive option. Of course, there is still a >> ton of setup work to do. But this does remove the cost barrier and >> makes things a bit easier in general. I don't know why I didn't >> realize this before. >> >> Eric >> >> >> >> On Wed, Jul 13, 2011 at 7:20 AM, Eric Merritt <[email protected]> wrote: >>> Dave, >>> >>> I have been looking at build bot as well https://continuous.io. >>> Continuous.io is the way to go If I could just get a mac vm from ec2. >>> But alas, the apple folks seem to be fully against OSX on any platform >>> that is directly on apple hardware. It makes sense for them I suppose, >>> but very annoying to me. I may end up with a mac mini co-location for >>> the mac builds and ec2 for the linux, eventual windows builds all >>> driven by build bot. Thats my best solution so far, now its just going >>> to be a fair amount of work to get there. >>> >>> Eric >>> >>> On Tue, Jul 12, 2011 at 9:54 PM, Dave Peticolas <[email protected]> wrote: >>>> 2011/7/12 Eric Merritt <[email protected]> >>>>> >>>>> Hello All, >>>>> >>>>> On my big list of Todos right after Jeringa, and Jeringa Sinan >>>>> integration is setup a multiplatform continuous integration solution. >>>>> Its a fairly big job and one that can be done concurrently with the >>>>> things that I am doing now. I am wondering if anyone would be >>>>> interested in handling this rather large task. Or at the very least, >>>>> perhaps someone could point me in the right direction of a fairly drop >>>>> in solution. The two big targets are OSX and Linux in various flavors, >>>>> with windows a 'nice to have' feature in the long run. It would be >>>>> insanely nice if it used something like eC2 (though that doesn't >>>>> support OSX) that will allow build slaves to be spun up as needed. If >>>>> no one else is interested its a task I will get to in a bit, but It >>>>> would be a huge help of some one was already taken this on. >>>> >>>> I think there are a number of these available. Two I know of are: >>>> Buildbot (http://trac.buildbot.net/) >>>> CruiseControl (http://cruisecontrol.sourceforge.net/). >>>> I've used buildbot quite a bit, not so much the other. >>>> >>>> dave >>>> buildbot quite a bit >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "erlware-dev" group. >>>> To post to this group, send email to [email protected]. >>>> To unsubscribe from this group, send email to >>>> [email protected]. >>>> For more options, visit this group at >>>> http://groups.google.com/group/erlware-dev?hl=en. >>>> >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "erlware-dev" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/erlware-dev?hl=en. >> >> > > -- > You received this message because you are subscribed to the Google Groups > "erlware-dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/erlware-dev?hl=en. > > -- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
