[Buildbot-devel] Multiple change sources and scheduler issues

[Neil Hemingway]

We already have schedulers setting Properties on builders, couldn't we
extend that to allow Changes to have Properties and then have those passed
on to the Build(Status) to be queried as needed?

A callback on the ChangeSource could set whatever Properties it wants.
Another on Scheduler can tell on the scheduler whether it's interested in
this change (think of it as a generalization of the branch check)

2008/7/23 Dustin J. Mitchell <dustin at zmanda.com>:

> On Wed, Jul 23, 2008 at 1:56 PM, Axel Hecht <l10n.moz at googlemail.com>
> wrote:
> > I saw you using categories in your example, how about re-using that
> > concept. Instead of using dicts with arbitrary values, we could use
> > list of strings. I confess, it'd be functionally equivalent, but less
> > complex to explain.
>
> I'd be down with that.  Maybe we could call them "change tags"?
> Neither of those words start with "B" or "S", and we don't use tags
> elsewhere in the project.
>
> Dustin
>
> --
> Storage Software Engineer
> http://www.zmanda.com
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20080723/f350db29/attachment.html>