What is bibisect? And what is it doing in my office?

[Jan Holesovsky]

Hi,

On 2012-06-16 at 02:22 -0700, bfo wrote:

> > The bibisect is only possible for Bugs which are reproducible under Linux,
> > if Linux has already been excluded (maybe bug history or comments will
> > contain required information) bibisecting will not be possible. But of
> > course, you can use bibisect to find out whether the bug is reproducible
> > under Linux. 
>
> What is needed to prepare a Windows version? There are Windows tinderboxes
> with daily builds of LO already (with new builds made twice a day even).
> Repacking them as ready to go Windows installation by using PortableApps
> technology would allow to do bibisecting on Windows without a hassle (if I
> understand correctly it is a manual run exe-check exe-mark source process).
> Am I missing something?

Not at all - it is even possible to generate a zipped installation, that
would be just unpacked, and checked into git; ie. nothing really hard to
do.  But nobody has done that yet - are you interested?

If yes: The best would be to modify the tinbuild2 to be able also to
commit the installation to a git repository, and push it to some
repository.  We wouldn't get the same granularity as a dedicated
bibisect build (with strict 64 commits interval), but still good enough,
considering that we usually have 40-100 commits a day.

The repository would have to be setup (on the server) to repack after
every push; but that is just a trivial hook.

The tinbuild2 is here:

http://cgit.freedesktop.org/libreoffice/contrib/buildbot/

You probably want to hack somewhere here:

http://cgit.freedesktop.org/libreoffice/contrib/buildbot/tree/bin/tinbuild_phases.sh#n85

(making it part of the do_push() function).

All the best,
Kendy