tagging releases

[Arne Babenhauserheide]

Am Donnerstag, 11. Dezember 2014, 18:29:02 schrieb Jensen, Aaron:

> We've resorted to using local tags. Because creating non-local tags
> creates a new revision, we had trouble reliably synchronizing that
> tag with the central repository (i.e. it would work most of the
> time, but when synchronization fails, builds stop working and
> requires manual intervention). At some point, we'll move to storing
> tags in some external system or create some process for converting
> the local tags to more permanent tags. In my experience, Mercurial's
> tag system isn't automatable from a configuration management
> perspective, unless your build server and central Mercurial server
> are using the same repositories (i.e people push to and pull from
> the same repository your build server uses when tagging).

Why don’t you use special bookmarks? hg bookmark tag-x.y

⇒ Build system checks whether the tag builds, and if yes, it creates the tag x.y.

Best wishes,
Arne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 299 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20141212/f0ee3472/attachment.asc>