[Buildbot-devel] Multiple change sources and scheduler issues

[Axel Hecht]

Our use case will be:

en-US/main code changes on the one side
l10n changes on the other, with, fasten your seat belt, a repo per
localization. So we'll end up with some 60 l10n repos.

We can name the changesources something like "l10n-af", "l10n-ar",
"l10n-be", but doing
dict(forrest="l10n", repo="af") would be prettier. So all our en-US
scheduler would pay attention for dict(repo="mozilla-central"), while
the l10n scheduler would pay attention to dict(forrest="l10n") and
would then set build properties based on the "repo" color to trigger
repacks for only a particular language.

I had a look, currently the changesources don't support names, so for
the size of the patch it will hardly matter if we use a single
property or a set of properties.

I'm not bound to 'color', btw, in particular the concept of some thing
having an arbitrary amount of colors is rather colorful ;-). Unless
you think of frequencies. But really, this is just me enjoying bending
my mind of that metaphor.

Axel

2008/7/23 Dustin J. Mitchell <dustin at zmanda.com>:
> On Wed, Jul 23, 2008 at 7:47 AM, Axel Hecht <l10n.moz at googlemail.com> wrote:
>> What do you guys think?
>
> I like the idea, but I haev to say, I really don't like the "color"
> terminology.  Also, it seems overly flexible.  Is there a use case
> which would not be satisfied by assigning one string to each
> ChangeSource (instead of many in a dictionary), and matching that
> against a list of strings in the scheduler?  If we do that, then we
> don't need a new metaphor -- we can just use the name of the
> ChangeSource object:
>
> c['change_source'] = [ ..
>  ChangeSource(name="foo", ..)
>  ChangeSource(name="bar" ..)
>  ChangeSource(name="ding", ..)
>  ..
> ]
>
> c['schedulers'] = [
>  Scheduler(changeSources=['foo', 'ding'], ...
>  ..
> ]
>
> Dustin
>
> --
> Storage Software Engineer
> http://www.zmanda.com
>