[Buildbot-devel] Buildbot fetching wrong revisions? [Bzr]

[Dustin J. Mitchell]

2010/1/5 Marcus Lindblom <macke at yar.nu>:
>> FYI, this thread [1] (Oct 2008) contained at least  two patches [2]
>> [3] for this feature ... None of them got any comments.
>>
>> [1] http://thread.gmane.org/gmane.comp.python.buildbot.devel/3654
>> [2] http://cache.gmane.org//gmane/comp/python/buildbot/devel/3681-001.bin
>> [3] http://article.gmane.org/gmane.comp.python.buildbot.devel/3683
> Too bad. No-one seemed to have picked up that. :(

The functionality in those patches is largely supported by the
existing "category" support.

There are a few major limitations to this technique, though.  The
notion of "latest" (revison=None) gets fuzzy, which I think is the
problem in the OP.  Also, unless SourceStamps carry the
category/name/repository/whatever tag along with them, the status has
no way to distinguish sourcestamps from different repositories.
There's no provision for interaction between versions, either - for
example, if Spam depends on Eggs, you'd probably want to rebuild Spam
on every commit to Eggs, but not vice versa.

If you see something missing in the category support that was present
in the patches, let me know -- I didn't see it, looking just now.

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com