Christian Lohmaier wrote: > Hi Eric, *, > > On Mon, Dec 11, 2006 at 08:37:05PM +0100, eric b wrote: >> [...] (snip) >> >> Comment : buildbots for Mac OS X + manual builds should be enough. >> I'm pretty sure this is the same for other archs :-) > > I know everybody is on the buildbot-hype - but don't forget about > tinderbox.. Tinderbox constantly builds everything without an explicit > request to do so. Hear, hear!
> Many buildbreakers can just be avoided by not integrating cws that break > the build. (Preventing is better than fixing afterwards) > > Tinderbox has a seperate overview page for cws that are in ready-for-qa > state[1]: > http://go-oo.org/tinderbox/ready_for_QA.express.html > > (main builders are two linux boxes (build everything), one PPC Mac > (builds everying) and one Windows-box (builds selected stuff)) The windows box builds all milestones and RC's. And CWS's if there is demand. So don't be shy and just send me an email if you want your CWS to be build on Windows. (If I find the time I'll integrate that box into the buildbot system, I promise ;) ) Volker > So before a cws gets nominated, I suggest that the QA-Rep has a look at > that page. If the cws is listed "green", then no problem, nominate it. > However if one or more are listed "red", then have a look at the logs > (tinderbox offers summarized logs as well as full logs) and see whether > the breaker is caused by the cws. > > You can ignore the "red" status if > * You added a new module (is not listed in EIS info and thus tinderbox > cannot know about it, the build will break because of that missing > module) > * the Master your cws is based on failed as well. Usually the > buildmaster of the buildslave will hunt for patches in IZ and apply > them to make the master build and then rebuild all relevant cws so > this should only last a couple of days) > > Apart from that, a build may occasionaly fail because of parallel build > issues, but that is the exception, not the rule. > If your cws is red, and the master is green, then something is fishy. > Have a look! > > If tinderbox didn't build your cws yet, fire up one of the buildbots to > fill the gap. > > Tinderbox buildslaves will always perform clean builds (as do the > buildbots). > > combinations of integrated cws may still cause build-breakers, but well, > that's life... > >> [...] > > ciao > Christian > [1] other overview pages are only "new" cws: > http://go-oo.org/tinderbox/new.express.html > and both ready and new: > http://go-oo.org/tinderbox/all_trees.express.html -- = http://wiki.services.openoffice.org/wiki/Debug_Build_Problems = PGP/GPG key (ID: 0x9F8A785D) available from wwwkeys.de.pgp.net key-fingerprint 550D F17E B082 A3E9 F913 9E53 3D35 C9BA 9F8A 785D
signature.asc
Description: OpenPGP digital signature
