On Sat, Nov 30, 2013 at 1:03 AM, Robinson Tryon
On Fri, Nov 29, 2013 at 11:00 AM, Norbert Thiebaud <firstname.lastname@example.org> wrote:
my intention is....
have some tb upload tar.gz installation regularely in a dumping zone
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?
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
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.
To unsubscribe e-mail to: email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy