[users at bb.net] Changes not being scheduled as expected

[Aran Deltac]

Hi all,

I emailed about this a long while ago and was not able to get to the bottom
of this issue.  Without a resolution I have just ignored the problem even
tho it rears its head at work all the time.  This issue has been used by
some people as a piece of why they'd like to move to Jenkins.  Whether we
go to Jenkins at some point or not, it would be great to figure out whether
1) my assumptions are incorrect, or 2) buildbot isn't working right.

I have a single GitPoller looking at 3 branches (a, b, and c).

I have 3 SingleBranchSchedulers (A, B, and C), each with a ChangeFilter
looking for changes in one of each of the 3 branches.

If I push a commit to branch *a* the change filter sees it and the build is
scheduled by the *A* scheduler.  Then I push the same commit to branch *b*
and the commit is ignored.  I have to manually schedule a build.

Do different Schedulers/ChangeFilters share a common log of what commits
have already been built?  If so, that would explain why my separate
schedulers ignore changes already handled by other schedulers.

I would expect schedulers to keep separate records of which changes they
have already processed, but that does not seem to be the case.  Is there
any way to make the schedulers have independent lists of which changes they
have already seen?

My previous email, subject "GitPoller/Scheduler Behavior Changed, Changes
Ignored", sent late last year, has more details.

Thanks for any thoughts,

Aran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/users/attachments/20160506/1824458a/attachment.html>