Development/Tinderbox

    From The Document Foundation Wiki

    For users

    Please note that many of the tinderboxes here are run by individuals just out of their personal interest, for as long as they have the resources, patience, interest etc, and there is no "official" guarantee that daily builds for some specific platform and configuration will continuously be built and uploaded.

    While TDF does run some official tinderboxes, there are a number of machines that are administered by community volunteers. We have some guidelines and naming conventions for builds to help users like you find the right build and configuration for your particular testing needs. The Document Foundation accepts and redistributes such builds from any trustworthy volunteer, but obviously we make no promises of continuity or quality for those tinderboxes.

    If a TDF tinderbox has not been uploading builds for the past few days, check out the entry in the table below before contacting the TB owner. It's possible that the machine is temporarily down, uploads are disabled, or perhaps the machine only uploads builds sporadically. While master gets commits every day, other branches may only be updated infrequently, especially as a release series nears EOL, so check the branches in gerrit to make sure a new build is expected :-)

    For build logs and other details, go to tinderbox.libreoffice.org, browse to a branch you are interested in and click "details" on builds to see further links. From the build logs you can find out, if the build you are using has been built using the --enable-dbgutil configuration option, for example.

    For Tinderbox owners

    Please register on this page. For tips how to setup your tinderbox, please have a look at the Tinderbox Setup page.

    Assign your tinderbox an unused id. If your tinderbox becomes inactive, please mark it as such, but do not remove the line so that your id is not accidentally re-used.

    Naming Your Tinderbox

    The name of your tinderbox (TINDER_NAME in the config) should follow this scheme:

    <target-os>-<target-version/flavor>-<target-arch>@<id>-extra_informations_in_free_form
    
    • Do not use @ in <target-os>, <target-flavor> or <target-arch>.
    • The <target-version/flavor> can be omitted if the platform does not have more means of installing packages.
    • Please be nice and avoid spaces in the box's name.

    Examples:

     macOS-x86_64@49/                           # A macOS buildbot with 64bit hardware
     Linux-deb-x86@26/                           # Linux buildbot that generates 32bit debs
     Win-x86@47-TDF/                             # Official TDF buildbot, running 32bit Windows
     Linux-rpm_deb-x86_64@46/                    # Linux buildbot that generates 64bit rpm and deb packages
     macOS-Intel@27-macOS_10.7.0-gcc_4.2.1_llvm/  # Mac w/Intel hardware
    

    Naming your Build

    Consistent naming in build filenames helps QA and Devs to work more quickly and efficiently. The build name should follow this scheme:

    <branch-name>_<OPTIONAL-debug>~<build-creation-date>_LibreOffice<release-build?>_<version-in-configure.ac>_<OS>_<arch>_<OPTIONAL-packaging-type>
    
    • If it's a debug build, "_dbg" is added after the <branch-name>
    • Note that a twiddle "~" follows the <branch-name> and <OPTIONAL-debug> (not a hyphen)
    • <build-creation-date> is in YYYY-MM-DD_HH.mm.ss syntax
    • <release-build?> is the empty string ("") if --enable-release-build, otherwise it's "Dev"
    • <OS>, <arch>, and <OPTIONAL-packaging-type> are defined by the build

    Examples (nudged into columns for clarity):

    libreoffice-4-3       ~ 2014-11-22_23.03.33 _ LibreOfficeDev _ 4.3.5.0.0      _ Linux _ x86-64 _ deb
    libreoffice-4-3       ~ 2014-11-14_11.58.13 _ LibreOfficeDev _ 4.3.5.0.0      _ MacOS _ x86           # Ideally would be 'macOS' for consistency w/tinderbox names
    master          _ dbg ~ 2014-11-13_22.50.19 _ LibreOfficeDev _ 4.4.0.0.alpha2 _ Linux _ x86-64
    master                ~ 2014-11-22_23.41.04 _ LibreOfficeDev _ 4.5.0.0.alpha0 _ Win   _ x86
    

    Examples (as build filenames):

    libreoffice-4-3~2014-11-22_23.03.33_LibreOfficeDev_4.3.5.0.0_Linux_x86-64_deb.tar.gz
    libreoffice-4-3~2014-11-14_11.58.13_LibreOfficeDev_4.3.5.0.0_MacOS_x86.dmg
    master_dbg~2014-11-13_22.50.19_LibreOfficeDev_4.4.0.0.alpha2_Linux_x86-64_archive.tar.gz   
    master~2014-11-22_23.41.04_LibreOfficeDev_4.5.0.0.alpha0_Win_x86.msi
    

    I think this is an example of incorrect naming:

    libo-43~2014-11-20_08.39.02_LibreOfficeDev_4.3.5.0.0_Win_x86.msi
    

    Parsing Tinderbox Names

    The tinderbox naming scheme is designed so that one can rely on the id to locate a specific download. You should only rely on the id, which can be parsed using the following pattern:

    @[0-9]+\-
    

    Status of Tinderboxes

    There is a page which states the status of the tinderboxes. That is http://tinderbox.libreoffice.org/MASTER/status.html

    List of registered Tinderboxes

    Key
    This tinderbox is Active
    This tinderbox is a Jenkins Slave
    This tinderbox is Inactive
    This tinderbox is Retired
    This tinderbox is in a Testing or trial or setup phase
    Libo-list-icon.png This is an Official TDF Tinderbox


    Tinderbox ID Active (Yes/No) Name Owner Tinderbox OS Build target OS CPU Cores RAM SSD
    1
    Retired macOS-Intel@1 nthiebaud@gmail.com macOS macOS
    Normally iterate within 15-20 minutes of a commit. Upload dailies
    2
    Retired Linux-Gentoo_x86_64@2 nthiebaud@gmail.com Gentoo Linux Gentoo Linux
    -
    3
    Yes macOS-Intel@3 thb@documentfoundation.org macOS macOS Intel Core 2 Duo 1.83GHz 2 2GB
    Normally iterate within 2-3 hours of a commit. Uploads dailies
    4
    Retired Linux-Fedora17-x86_64@4 thb@documentfoundation.org Fedora Linux Fedora Linux
    Decommissioned
    5
    Retired Android-ndk7@5 thb@documentfoundation.org ? ?
    Decommissioned
    6
    No Win-x86@6 kendy@collabora.com Windows Windows
    Incremental, uploads dailies, runs tests.
    7
    Retired Win-x86@7 kendy@collabora.com Linux Windows
    Iterates within 1-2 hours of a commit. This is highly experimental build, it creates Windows binaries on Linux (via MinGW and cross-compilation). Please make tdf#41883 depends on the most annoying bugs specific to these builds.
    8
    No Linux-x86-64@8 N/A Linux Linux
    Iterates within 1-2 hours of a commit. Builds only, does not upload dailies.
    9
    Retired Win-x86@9 nthiebaud@gmail.com Windows Windows
    Voreppe's Box. Builds libreoffice-3-6 branch. Iterates within 9-10 hours of a commit. upload dailies
    10
    Yes Linux-x86_10-... fstrba@suse.com Linux Linux
    Linux Release configuration x86. upload dailies
    11
    Yes Linux-x86_64_11 fstrba@suse.com Linux Linux
    Linux Release configuration x86_64. upload dailies
    12
    Retired macOS-PPC@12 thb@documentfoundation.org macOS macOS
    Decommissioned due to HW failure
    13
    Yes macOS-PPC@13 lohmaier+tinderboxPPC@googlemail.com macOS PPC macOS PPC
    installsets only on request
    14
    Retired Linux-F19-x86_64@14 sbergman@redhat.com Fedora 21 Fedora 21
    Clang trunk (towards 3.7); --enable-compiler-plugins, --enable-dbgutil, make check screenshot; takes ca. 8 hours
    15
    Retired Win-x86@15 fridrich.strba@bluewin.ch Windows x86 Windows x86
    Builds libreoffice-3-5 branch, uploads dailies.
    16
    Slave tb16 nthiebaud@gmail.com Windows 2008 R2 Windows 2008 R2
    -
    17
    No Win-x86@17 noelgrandin@gmail.com Windows 7 Windows 7
    Builds master
    18
    {{{active}}} Linux-openSUSE-x86@18 N/A openSUSE openSUSE
    Clang compiler with LO compiler plugin, 32bit, massively parallel (icecream), runs tests
    19
    No Linux-openSUSE-x86@19-GCC N/A openSUSE openSUSE
    The same setup like the clang tinderbox (@18), except for the compiler, builds only when the clang tinderbox has a build failure
    20
    Slave tb20 nthiebaud@gmail.com Windows 2008 Windows 2008
    This is a Jenkins Slave Bot
    21
    Yes macOS-10.8@21 nthiebaud@gmail.com macOS macOS
    This is a mac, that do gerrit and tb based build. for master and typically the latest release branch.
    22
    Yes Linux-Fedora-x86_64@22 caolanm@redhat.com Fedora Linux Fedora Linux
    This is an incremental builder, the idea here is to capture any failures in an incremental build that don't affect a from scratch build so we can improve our dependency tracking as affecting the ordinary hacker.
    23
    Yes Linux-Gentoo-x86_64@23 tchvatal@suse.cz Gentoo Linux Gentoo Linux Intel(R) Core(TM) i7-2600 8 16G
    Tinderbox building the master with all possible system libs enabled (except those that are not released/stable yet). Build takes ~40 minutes from scratch.
    24
    Yes Android-ARM@24 cloph? Debian x86_64 Android on ARM AMD Opteron 8
    Cross-builds master for Android/ARM. The build system is an 8-CPU AMD64 running Debian.
    25
    No Android-X86@25 tml@iki.fi Debian x86_64 Android on x86 AMD Opteron 8
    Cross-builds master for Android/x86. The build system is an 8-CPU AMD64 running Debian.
    26
    No Android-MIPS@26 tml@iki.fi Debian x86_64 Android on MIPS AMD Opteron 8
    Cross-builds master for Android/MIPS. The build system is an 8-CPU AMD64 running Debian.
    27
    Yes macOS-Intel@27 thb@libreoffice.org macOS 10.9.4 macOS Intel Core i5 2.3GHz 2 8GB
    Normally iterate within 2-3 hours of a commit. Uploads dailies, runs tests. LeFontanil's Box
    28
    No iOS-Simulator@28 tml@iki.fi macOS iOS
    Builds for the iOS simulator.
    29
    No iOS-ARM@29 tml@iki.fi iOS on ARM
    Builds for iOS device.
    30
    No macOS-X86_64@30 tml@iki.fi
    Builds 64-bit code for macOS.
    31
    Yes Linux-x86_64@31-Release-Configuration-RHEL5-Baseline caolanm@redhat.com RHEL5 x86_64 Generic Linux x86_64
    64-bit libreoffice-4-0 release mode builds for universal Linux deployment. Uploads dailies.
    32
    Yes Linux-x86_64@32 matus.kukan@gmail.com Fedora Linux Fedora Linux
    Incremental build. Then runs "loperf" - performance tests; uploads callgrind generated profile data.
    33
    No Linux-Ubuntu-12.04@33 nthiebaud@gmail.com Ubuntu 12.04 Ubuntu 12.04
    Aquinetic donated buildbot. gerrit builbot for master
    34
    Yes Linux-x86@34 caolanm@redhat.com RHEL5 Generic Linux x86
    32-bit libreoffice-4-0 release mode builds for universal Linux deployment. Uploads dailies.
    35
    No Raspbian-ARM@35 matus.kukan@gmail.com ?? Raspbian on ARM
    Cross-builds master for Raspberry Pi/Raspbian. Uploads dailies.
    36
    No macOS-X86@36 tml@iki.fi macOS x86 macOS x86
    Builds 32-bit code for macOS. Uploads dailies. In no way "official".
    37 Libo-list-icon.png
    Yes macOS-X86@37 nthiebaud@gmail.com macOS macOS
    Gerrit buildbot tdf-owned hardware.
    38 Libo-list-icon.png
    Yes Win-X86@38 markus.mohrhard@googlemail.com Windows Windows Intel Core i7 3770k 3.5GHz 4 16GB Yes
    Gerrit buildbot tdf-owned hardware.
    39 Libo-list-icon.png
    Yes Win-X86@39 dennisroczek@libeoffice.org Windows Windows
    Gerrit buildbot tdf-owned hardware.
    40 Libo-list-icon.png
    Testing Linux-Ubuntu-12.04@40 thb@documentfoundation.org Ubuntu 12.04 Ubuntu 12.04 Intel Core2 Quad 3GHz 4 8GB
    Gerrit buildbot tdf-owned hardware.
    41 Libo-list-icon.png
    Testing Win-X86@41 cloph@documentfoundation.org Windows Windows
    Gerrit buildbot tdf-owned hardware.
    42 Libo-list-icon.png
    Yes Win-X86@42 thb@documentfoundation.org Windows Windows Intel Core i7 3770k 3.5GHz 4 16GB Yes
    Gerrit buildbot tdf-owned hardware.
    43
    No macOS-X86_64@43 andrzej@ahunt.org macOS macOS Core 2 Duo P8600 2 2GB
    Currently failed, should hopefully be fixed by end of 2013.

    macOS-X86_64_43 on master builds within a desktop session, all other profiles (macOS-X86_43 on master/4.1/4.0) build in a non-graphical session.

    44
    No Linux-openSUSE-x86_64@44 N/A openSUSE openSUSE
    Runs tests (including JUnit)
    45 Libo-list-icon.png
    Yes Linux-rpm_deb-x86@45 cloph@documentfoundation.org Linux Linux virtualized (kvm host: i7-4770) 8 3GB
    Builds done on release-baseline, does dailies
    46 Libo-list-icon.png
    Yes Linux-rpm_deb-x86_64@46 cloph@documentfoundation.org Linux Linux virtualized (kvm host: i7-4770) 3 3GB
    Builds done on release-baseline, does dailies
    47 Libo-list-icon.png
    Yes Win-x86@47 cloph@documentfoundation.org Windows Windows virtualized (kvm host: i7-3770) 8 8GB
    Builds done on release-baseline (up to 4.2.x), does (almost) dailies
    48
    Yes Linux-Debian-armhf@48 andrzej@ahunt.org Debian Debian Exynos 5 Octa (Exynos 5410) 4 Enabled 2GB Yes
    ODroid-XU
    49 Libo-list-icon.png
    Yes macOS-x86@49 cloph@documentfoundation.org macOS macOS i7-3720QM 4 (8 threads) 16GB Yes
    does dailies
    50 Libo-list-icon.png
    No Linux-with-check@50 markus.mohrhard@googlemail.com Linux Linux
    executes chart shapes tests, make check and export validation
    51 Libo-list-icon.png
    Yes Win-x86@51-TDF cloph@documentfoundation.org Windows Windows virtualized (virtualbox host: i7-3720QM) 8 8GB Yes
    Builds done on release-baseline (4.3 and 4.4, VS2012); does (almost) dailies, based on load (ping if no build for 4+ days)
    52
    No Linux-x86_64@52 tml@iki.fi openSUSE openSUSE
    -
    53
    Retired macOS-10.9-x86_64@53 robert.buj@gmail.com macOS Mavericks macOS Mavericks Intel Core i7 2620M 2.7GHz 2C/4T 16GB Yes
    Both target and host operating systems were superseded by macOS Yosemite on October 17th, 2014. Prior this date, it built dailies incrementally for macOS Mavericks and it ran in tinderbox mode with running tests enabled.
    54
    Retired Linux-Ubuntu-x86_64@54 kb9vqf@pearsoncomputing.net Ubuntu Linux 14.04 Ubuntu Linux 14.04 with TDE support enabled E3-1270 V2 @ 3.50GHz 1 2GB
    Retired due to TDF dropping TDE support. Previous info: Builds done against MASTER. Does dailies.
    55 Libo-list-icon.png
    No macOS@55 markus.mohrhard@googlemail.com macOS macOS
    TDF owned Mac Mini
    56
    Yes Linux-deb-x86@56 v-itm-libreoffice-tinderb@muenchen.de Ubuntu 12.04 Ubuntu 12.04
    using gcc 4.6
    57
    Slave tb57 nthiebaud@gmail.com macOS 10.9 macOS 10.9
    -
    58
    Slave tb58 nthiebaud@gmail.com macOS 10.9 macOS 10.9
    -
    59
    Slave tb59 nthiebaud@gmail.com macOS 10.9 macOS 10.9
    -
    60
    Slave tb60 nthiebaud@gmail.com macOS 10.9 macOS 10.9
    -
    61
    Retired macOS-10.10@61 robert.buj@gmail.com macOS Yosemite macOS Yosemite Intel Core i7 2620M 2.7GHz 2C/4T 16GB Yes
    Both target and host operating systems are macOS Yosemite from October 17th, 2014. It builds dailies incrementally and it runs in tinderbox mode.
    62 Libo-list-icon.png
    Yes Win-x86@62-TDF cloph@documentfoundation.org Windows Windows virtualized (kvm host: i7-3770) 8 8GB Yes
    Builds done on release-baseline (master, VS2013); does (almost) dailies, based on load (ping if no build for 4+ days)
    63 Libo-list-icon.png
    Retired tb63 nthiebaud@gmail.com Centos7 64bits Centos7 64bits
    VM on Manitu
    64 Libo-list-icon.png
    Retired tb64 nthiebaud@gmail.com Debian7 64 bits Debian7 64 bits
    VM on Manitu
    65 Libo-list-icon.png
    Retired tb65 Windows-2012R2 Windows-2012R2
    Decommissioned EC2 c4.x4large instance
    66 Libo-list-icon.png
    Slave tb66 nthiebaud@gmail.com macOS macOS
    MacPro 8-core
    67
    Testing macOS-10.11@67 robert.buj@gmail.com macOS El Capitan macOS El Capitan Intel Core i7 2620M 2.7GHz 2C/4T 16GB Yes
    Both target and host operating systems are macOS El Capitan from June 9th, 2015. It builds dailies incrementally and it runs in tinderbox mode.
    68 Libo-list-icon.png
    Slave tb68-Bytemark nthiebaud@gmail.com Windows-2012R2 Windows-2012R2
    Dual-socket E5530, 16 cores provided by Bytemark
    69 Libo-list-icon.png
    Retired tb69 brett@libreoffice.org macOS 12 (Monterey) macOS 12 (Monterey) 2.7 GHz Intel Xeon E5 12 32 GB 1866 MHz DDR3 Yes
    Mac Pro (late 2013). Failed CPU (both CPU lights are illuminated, would not boot).
    70 Libo-list-icon.png
    Yes Linux-rpm_deb-x86_64@70 cloph@documentfoundation.org Linux Linux virtualized (kvm host: AMD Opteron 62xx) 8 8GB
    Builds done on release-baseline (CentOS 6, master), does dailies
    71 Libo-list-icon.png
    Yes Linux-rpm_deb-x86@71 cloph@documentfoundation.org Linux Linux virtualized (kvm host: AMD Opteron 62xx) 8 8GB
    Builds done on release-baseline (CentOS 6, master), does dailies
    72 Libo-list-icon.png
    Slave tb72 nthiebaud@gmail.com Windows-2012R2 Windows-2012R2 Dual Intel Xeon E5-2640v3
    -
    73 Libo-list-icon.png
    Slave tb73 nthiebaud@gmail.com Windows-2012R2 Windows-2012R2 Dual Intel Xeon E5-2640v3
    -
    74 Libo-list-icon.png
    No tb74 nthiebaud@gmail.com CentOS 7 CentOS 7
    EC2 c4-4xlarge instance
    75 Libo-list-icon.png
    Slave tb75 nthiebaud@gmail.com CentOS 7 CentOS 7
    lilith@manitu
    76 Libo-list-icon.png
    Slave tb76 nthiebaud@gmail.com CentOS 7 CentOS 7
    maggie@manitu
    77 Libo-list-icon.png
    No tb77 jluth@mail.com Ubuntu 16.04 Ubuntu 16.04 i3-4160 2 (4 threads) 4GB
    hopefully Linux bibisect max series for the missing 5.x
    78 Libo-list-icon.png
    Yes callgrind nthiebaud@gmail.com and markus.mohrhard@googlemail.com Fedora Fedora 6 12GB
    Jenkins Callgrind tinderbox -- perf.libreoffice.org
    79
    Yes Linux_x86_64@79-ubuntu16-collabora andras.timar@collabora.com Ubuntu Ubuntu AMD EPYC 7401 24 128GB
    Online dist tarball
    80 Libo-list-icon.png
    Yes updater markus.mohrhard@googlemail.com SLES 12 SLES 12 8 16GB
    Producing automatically updating Linux daily builds; Runs at gandalf through jenkins
    81
    Yes Linux_x86_64@81-ubuntu1804-collabora andras.timar@collabora.com Ubuntu Ubuntu AMD EPYC 7401 24 128GB
    Online debug + make check
    90
    No tb90 brett@libreoffice.org macOS 12 (Monterey) macOS 12 (Monterey) 2.4 GHz i9-9980HK 8 32GB DDR4 2667 MHz Yes
    A2141 (2019)
    91
    Retired tb91 brett@libreoffice.org CentOS 7 CentOS 7 4.00Ghz Intel i7-6700k 8 16GB 3200 MHz DDR4 Yes
    Failed hardware
    93 Libo-list-icon.png
    Slave tb93 brett@libreoffice.org macOS macOS Apple M1 8 8GB Yes
    -