On Fri, Jul 31, 2009 at 11:31 AM, Peter FELECAN<[email protected]> wrote: > "Maciej (Matchek) Blizinski" <[email protected]> writes: > >> On Fri, Jul 31, 2009 at 10:00 AM, Peter FELECAN<[email protected]> wrote: >>> "Maciej (Matchek) Blizinski" <[email protected]> writes: >>> >>>> - buildbot can handle parallel builds on the buildfarm, by running >>>> different builds in different subdirectories >>> >>> This should be done on a different system than that used for day to day >>> work. I don't want to be penalised by gcc, OpenOffice and other monsters >>> being built the same time that I wish to build a new package. >> >> I see two potential solutions: >> >> 1. Provide separate hardware for the buildbot > > +1 (I know, I'm not paying the bill) and please, not a zone or a VM on > the same hardware... > >> 2. Avoid building certain blacklisted packages. Optional: schedule >> periodic or nightly builds for those packages. > > -1 as it defeats the purpose; in addition, there is no night for an > international community as ours...
Automatic builds for some packages are better than automatic builds for no packages, so it doesn't defeat the purpose completely. Also, we could do actual measurements: how big is the impact on the performance? >>>> - buildbot automatically picks up changes from the repository, there's >>>> no hand-scheduling needed >>> >>> This is true only for "garified" packages. Is there a plug-in for other >>> kind of build? >> >> Can you come up with an example of a different build? Where would the >> source code come from? > > All my packages are outside gar. The source code comes from my home > directory... How would you make your source code available to buildbot? Maciej _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers
