On Sat, Nov 30, 2013 at 1:03 AM, Robinson Tryon <bishop.robin...@gmail.com> wrote: > On Fri, Nov 29, 2013 at 11:00 AM, Norbert Thiebaud <nthieb...@gmail.com> > wrote: >> my intention is.... >> have some tb upload tar.gz installation regularely in a dumping zone >> per platform >> have a cron to regularely.. scrupt these upload zone(*) and >> consolidate things in a bibisect repo > > Why not have the tb push builds directly into the bibisect repo? > https://wiki.documentfoundation.org/Development/tb#Variables
because... 1/ keeping a local bibisect repo on each tb would be expensive in, if nothing else, bandwidth 2/ multiple tb upload stuff.. synchronizing htem can be difficult, especially with wide variation in upload bandwidth 3/ the order of commit in the bibisect matter. 4/ experience shows that somethings things break for some minor details.. being able to fix things an recover using staged build is useful 5/ having some kind of control over the bibisect buidling as it build is good. it is easier to do when a centralized script do the job.. then one can review the log and decide to re-do thing if need be, before the problem is buried too deep. _______________________________________________ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
