Development/Tinderbox

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: --@-extra_informations_in_free_form


 * Do not use @ in ,  or .
 * The  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: _~_LibreOffice___ _


 * If it's a debug build, "_dbg" is added after the 
 * 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, otherwise it's "Dev"
 * <OS>,, 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