QA/Testing Daily Builds
LibreOffice provides so called Daily Builds for testing program versions between the official releases. Here you can get all information you need for conducting such tests.
The location of the daily builds
You will find the daily builds in dev-builds.libreoffice.org/daily
Appimage versions are available for Linux users who prefer them.
The SI-GUI installation tool may also be used to conveniently download and install daily builds (currently for Windows and Android).
Daily builds are available for Windows, macOS and Linux. Please see the list of registered tinderboxes for more details.
Using daily builds
Daily builds install and run in parallel to a normal release version
See the article Installing in parallel. Windows daily builds do not need any special steps - they always install separately.
Testing different languages
To try LibreOffice in different languages, without changing the configuration, you can use the command line parameter
For example, to set the default language to French:
When reporting against a master build, use the version with alpha0+ Master at the end.
Copy and paste the contents of your Help - About to your report. It includes the tinderbox number.
For general bug reporting advice please see BugReport'!
Builds are typically produced by tinderboxes. So they come from anyone running a tinderbox that has ssh access to the server hosting dev-builds. LibreOffice.org can upload dailies.
The frequency of the uploads
If the tinderbox script is setup as such, it will attempt the upload after the first successful build of the day (that is after 00:00 UTC).
The frequency varies, ideally it is once per day. However, that might not be the case for three main reasons:
- the tinderbox is down
- the tree being built is broken and no build succeeded that day
- there was no activity in that tree during that day.
The directory 'current' should link to the latest available build.
There is no naming convention at this point for tinderboxes, but most are named in a way that should allow one to guess what they are. If you want to know exactly what options are used you can refer to tinderbox MASTER status page and look at the build log for the tinderbox you are interested in.
For instance the build log starts with:
1 2 2011-10-28 23:14:15 3 core:2a5e99cb83a91e9a4bb92c117dcbc8baa6d718fe 4 binfilter:522e9fe9e46e52f4c7ac48858ee6cd82a2e0eb48 5 dictionaries:c4051ff3fff35db559e3363e6728f6bc3f9de071 6 help:3b66bd0d5781edd556817fd443dbf69a892cd066 7 translations:672ed497054a4d92a620e615bbaa18313c06f919 8 running ./configure with ´--with-num-cpus=4´ ´--with-max-jobs=5´ ´--disable-mozilla´ ´--without-system-mozilla´ ´--disable-binfilter´ ´--disable-kde´ ´--with-jdk-home=/opt/sun-jdk-18.104.22.168´
Here you can see exactly what was built (the git-sha of each repo) and the exact list of configuration options used to build.