Automatic tagging

[Roman Kennke]

I have a problem for which I don't have a reasonable clean solution with
Mercurial.

Suppose you have Mercurial setup in a way so that there is a central
repository, with all the team members working on clones of that. Also,
there is an automatic build system, which regularily clones the master
repository and tries to build it, and in case of success, sticks a tag
on the successful revision. Infact it moves one tag. This tag means
'This revision is known to build and passes through a basic testsuite'.

Now, with Mercurial there is one problem. How can the autobuilder
automatically tag the repository in a reliable way? I mean, it can tag
its cloned copy. But the tag needs to be pushed to the master
repository. However, this will likely abort, and a merge will be needed.
Merging is not what I would trust a script to do safely. To make matters
more difficult, I need to do that not only on a single repository, but
on a forest (optional for the start). Any ideas? What would be an
appropriate HGish way to implement such thing?

Cheers, Roman

-- 
Dipl.-Inform. (FH) Roman Kennke, Software Engineer, http://kennke.org
aicas Allerton Interworks Computer Automated Systems GmbH
Haid-und-Neu-Straße 18 * D-76131 Karlsruhe * Germany
http://www.aicas.com   * Tel: +49-721-663 968-0
USt-Id: DE216375633, Handelsregister HRB 109481, AG Karlsruhe
Geschäftsführer: Dr. James J. Hunt