[Buildbot-devel] Merging buildrequests and custom build properties

[Axel Hecht]

2008/5/22 Dustin J. Mitchell <dustin at zmanda.com>:
> On Thu, May 22, 2008 at 6:10 AM, Axel Hecht <l10n.moz at googlemail.com> wrote:
>> Comments? Oh, and, Dustin, sorry for not looking at that earlier.
>
> No problem!
>
> It seems to me that you don't want to merge BuildRequests, and in fact
> there are lots of reasons not to do so.  So maybe we need some way of
> configuring buildbot not to merge BuildRequests.
>

The funky piece is, I might want to. More details:

I'm doing l10n repacks of en-US builds, roundabout some 60 languages
in the case of Firefox. Not all of them released, if you're curious.
An en-US check-in rebuilds all, a check-in from a localizer just that
locale. A single build pass over all locales currently takes
roundabout 2.5 hours on windows.

Now, there are a bunch of scenarios, but what can happen is that the
slaves are still busy repackaging Danish and German while there is a
new check-in coming in for Turkish, which has an existing build
request pending. Now, I want the scheduler to send out a buildrequest,
and I want the Turkish build to merge, and to use a later source
stamp. I currently hacked something fiddlish to do that.

Looking at process.builder.Builder, we could add an option to that to
merge back, forth, or not. Like, currently, the way the merging is
done is that the Builder would build a later source step while there
may be build requests for the older sourcestamp still in the queue.

For the buildrequests, I'd propose to only merge if the source stamps
merge, and if the properties are the same.

Do I make any sense?
http://wiki.mozilla.org/User:AxelHecht/Building_l10n#Current_arch_on_l10n.m.o
has imagery and some descriptions, but they might not clear things up,
either. If you look, the BuildDesc objects would get replaced with
custom buildproperties.

Axel