On Oct 29, 6:48 pm, Mike Witt <msg...@gmail.com> wrote: > > Is there any chance of you making any of these machine which do *not* > > run Fedora 13 available to the build bot? There are 5 machines which > > the buildbot uses which runs Fedora 13, but nothing for Fedora 11, 12 > > or 14. > > Well, the one that runs Fedora 13 is the one that has the worst > problems building sage :-) But, anyway, I would love to do that. > The problems amount to things like all my machines are behind > one dynamic address from Quest. Only one machine is guaranteed > to be connected, and so on. > > I don't suppose there's a way I can initiate the "buildbot" > from my end and have the results go to the right place? > > Once I get time to install Fedora 14, I imagine I could at least > make that system available. I suppose that I should try to > understand how the "buildbot" scheme works. Is there one place > you can point me to that describes it pretty well? If so, I > could probably find an hour or two Saturday or Sunday to see > if I can understand its workings and then give you a > more coherent answer.
OK, well I did find the documentation on buildbot.net, and if I'm understanding correctly from my brief scan of some of the manual it appears that the communication is initiated from the build slaves. So, I think that means that my machines could be used. So I have two questions: (1) Do the machines have to be available all the time, or can they just be available some of the time. (2) Would someone be willing set this up for me (or at least provide an example "configuration" that works for sage builds on some linux type box) or will I have to *actually* study the buildbot manual until I can figure out how to do that myself. -Mike -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
