Hi Mathias, *, On Thu, Feb 26, 2009 at 10:59 AM, Mathias Bauer <nospamfor...@gmx.de> wrote: > Thorsten Ziehm wrote: >> >> I do not see the need to bring the build bots near to the build >> environment here in Hamburg. The request for build bots was (as I know) >> to have builds in different environments to find build issues in these >> different environment. When these environment will be nearly the same, >> then we miss to find these build breakers. > No, you are mixing build bots and Tinderbox builds. But even if we used > Build Bots in that way, I don't see any reason for "either-or".
Well, there's no sharp line between tinderbox and buildbots in general. Yes, tinderboxes are only for building (but that doesn't imply they don't generate perfectly suitable builds, just that their bandwidth just doesn't allow for uploading of installsets or wasting bandwidth for the steady connection to the buildbot master) On the other hand, buildbots are of course not only sources of installable builds - it would be a waste if the build-results would not be collected and taken into account.. Buildbots and tinderboxes *both* serve the purpose of checking whether a cws introduces build-breakers. tinderboxes do so exclusively, for buildbots it depends on the focus of the specific bot. Some can be seen as "installset providers" (and that is what requested here: Dedicated bots that provide installsets comparable to the ones provided as releases/snapshots) and others as tinderboxes that can be asked for an installset. I don't see "black and white" here. In the current situation, with Sun using a different toolchain (not only wrt. configure in OOo, but also the compiler, third-party libs OOo is compiled agains) Ideally there would be a "sun environment" buildbot in addition to the existing ones (one that doesn't build each and every cws, but provides installation-sets on request). So whether Sun switches to community build-env or not is not /that/ important to make the community-testers happy. (would of course be a good thing for various other reasons). The o3-iso was a little step in creating such an installset-provider-bot - but as it was not updated and incomplete, the bot cannot build any current tree and thus is offline. ciao Christian and for completion: Of course also tinderboxes can provide installsets [they can easily add a download-link to the log that is then shown in the build-result box) - there just is no "request a build"-webinterface --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
