[Buildbot-devel] Blamelist includes non-important changes?

[Axel Hecht]

2009/3/6 Greg Ward <gerg.ward+buildbot at gmail.com<gerg.ward%2Bbuildbot at gmail.com>
>

> Hi all --
>
> I've recently implemented my first "continuous" build, and was a
> little surprised by one detail.  Specifically, this build is triggered
> by changes to a small subset of our tree that doesn't change very
> often.  (I think of it more as "change-triggered" than "continuous".)
> So I implemented a fileIsImportant() function that returns false for
> most of our commits.  As a result, we can have dozens of commits
> covering many days before we see a change that actually triggers a
> build.
>
> What surprised me is that all of those commits are considered input to
> the build, and all of users who made those commits are on the
> blamelist... even though most of them have not touched the files that
> trigger a build and have nothing whatsoever to do with the success or
> failure of the build.
>
> Is this the intended behaviour?  Is there an easy way to trim the list
> of changes in a build to the "important" ones?
>

I ended up subclassing the scheduler to get rid of that behaviour.

I'm not actually sure why the behaviour is as is, though.

Axel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20090306/e95c8027/attachment.html>