[Buildbot-devel] monitoring and tagging multiple git repositories

[Evan Driscoll]

On 6/11/2011 15:39, Dustin J. Mitchell wrote:
> One generalization I've been toying with for a while is an "aggregate
> sourcestamp", which would be a sourcestamp that includes revision
> information for a whole tree of repositories.  In your case, your
> ChangeSource would produce changes for single repositories, and a
> specialized scheduler would use those changes to evolve a sourcestamp
> that represents the latest revision in each repository, and then kick
> off builds with that sourcestamp.

Since I also have the issue of dealing with multiple repositories (in
one case, several SVN repos; in another, SVN + Git), I also have an
interest in seeing support for this.

One question I've thought about is how possible it would be to take a
page out of CVS's book (something I don't recommend doing often :-)) and
use a *time* for the sourcestamp when multiple repositories are involved.

Barring issues like CVS's "commits aren't atomic", is there wide support
for this across version control systems? How hard would it be to hack
this in, even if it's a temporary solution (maybe even an unsupported
patch) until a better one is implemented?

Evan Driscoll

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 552 bytes
Desc: OpenPGP digital signature
URL: <http://buildbot.net/pipermail/devel/attachments/20110612/081db8ea/attachment.bin>