[Buildbot-devel] multiple change sources

[Axel Hecht]

2008/2/20, Dustin J. Mitchell <dustin at zmanda.com>:
> On Wed, Feb 20, 2008 at 1:43 AM, Minesh Patel <mipatel at vmware.com> wrote:
>  >  I have multiple change sources(P4, SVN) to monitor and I noticed that the
>  >  schedulers are not tied to any specific change source, so each Scheduler
>  >  receives change notifications from both P4 and SVN. How could I go about
>  >  receiving P4 changes to P4 schedulers and SVN changes to the SVN scheduler?
>  >  Is there a way to tie a change source to a scheduler, or will I have to use
>  >  the fileIsImportant attribute of the scheduler to filter changes.
>
>
> Currently, schedulers and ChangeSources are not associated with one
>  another.  There was some talk on the list recently about changing that
>  -- such a change would be well-received, I think, if you want to write
>  a patch.  That said, your fileIsImportant technique will work.

When I did that a while back, I got stuck with the fact that
fileIsImportant does keep the scheduler from triggering, the changes
will be included in the build request from the ignoring scheduler,
though. So if you really want to fork one change to one scheduler, and
another in another, and not see those changes in the other build
process, you'll need to hack deeper.

Axel