[Buildbot-devel] monitoring and tagging multiple git repositories

Dickon Reed dickon at cantab.net
Sun Jun 12 12:31:03 UTC 2011

A common concern (I know people on my project car) is that people get
nervous when there is version information canonically in an automation
system such as Buildbot, because they wish to maintain visibility through
the version control systems of what exactly went into each automated build,
and the ability to build manually. I think most version control systems
support symbolic tags and in some cases people probably want the aggregate
sourcestamp stored.

If we maintain the correspondence between change sources and repositories
(unlike in my experimental branch), then perhaps when the scheduler kicks
off a build with an aggregate source stamp there should be a callback from
the scheduler to each change source to give the change source an opportunity
to associate a symbolic tag for the build version with the revision of its
repository that is being built.  That would actually be better for my
project than my first idea to put everything into a git change source since
we do have some upstream sources using Mercurial.

Support in the web interface for requesting builds according to a symbolic
tag that is present in each repository may also be useful in some cases. It
would also be useful to see some indication of the aggregate source version
and the symbolic tag associated with it in the waterfall.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20110612/404e438f/attachment.html>

More information about the devel mailing list