Thats a killer argument. The master should be available more or less all the time to any erlware participant. So I could do something like a slicehost (just some cheap vps solution) or put it on our existing server (though that is shared), then have this box I will build serve the mac osx image. Then the box doesn't have to be that expensive. I may need to do some tunneling to get it all to work, but given the availability constraint that is probably the best way to go all around.
On Thu, Jul 14, 2011 at 12:27 PM, Salomon Elizondo <[email protected]> wrote: > I agree with the cost analysis, but a mostly hosted solution would be > easier to share with other contributors. Unless you already have your > home network nicely segmented. > > On Thu, Jul 14, 2011 at 12:07 PM, Eric Merritt <[email protected]> wrote: >> That would work probably rather well. I would still need a box at >> home, but it could be a cheaper box. Thats a good thing. Though I >> don't think a long running master should be on ec2. For things that >> need to endure, especially things with low over head ec2 isn't really >> very cost effective. Now that said, if I have to run a box at home, I >> could run the master there and the OSX slave, and use ec2 for the >> windows and unix variants. In the very long run it *might* be cheaper >> to buy a bigger home box and run vms on it. However, thats probably >> the very very long run considering each build might cost a couple of >> cents. While the home box is a fixed cost + power and the power isn't >> going to vary much between a little box that needs to run all the time >> and a bigger box that needs to run all the time. >> >> I suspect if I have to run a box at home, the win is just to do it all >> at home. If I can figure out how to get access to an always on OSX box >> or an OSX vm stored elsewhere the win is ec2. >> >> On Thu, Jul 14, 2011 at 11:57 AM, Salomon Elizondo <[email protected]> >> wrote: >>> with some tunneling gymnastics you can make your OSX slave bot (at >>> home) accessible to master on ec2 and have the other unix flavors on >>> ec2. >>> >>> On Thu, Jul 14, 2011 at 11:49 AM, Eric Merritt <[email protected]> >>> wrote: >>>> 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. >>>> >>>> >>> >>> -- >>> 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.
