Pushing tags to clones from tags?
Danny Tuppeny
danny at tuppeny.com
Sat Oct 1 11:17:49 UTC 2011
On 1 October 2011 12:05, Danny Tuppeny <danny at tuppeny.com> wrote:
> Ok, I just realised that our build server is running 1.7 due to the bug
> with #tag in URLs that was broke in 1.9. So, at home I just installed 1.9.2
> and tested this out. It now works more like I'd expect:
>
> - Clone http://blah/Repo#MyTag
> - Run "hg tag MyNewTag"
> - Run "hg out"
>
> This now shows the MyNewTag tag as outgoing, as I hoped. However, when I
> try to push, I get "creates remote heads". I guess this makes sense, however
> if I push it, presumably anyone that clones the repo will now have a head
> for each release tag, which is crazy. What's the preferred way to create a
> tag for a non-head changeset and push it into the repo?, Eg:
>
> - Commit some code
> - Tag as possible-next-release
> - Commit more code while possible-next-release is being tested by QA
> - QA give the go-ahead, need add a Release-1.1 tag to where
> possible-next-release was (not a head)
>
> Does this make sense?
>
Blond moment here... I don't have to tag from the revision I'm tagging, and
if I don't merge the heads, the tag wouldn't ever show up for people on the
"main" head. They should ofcourse be merged, but that might results in a
weird history.
I think without making changes to CruiseControl (or having some nasty
command-line app to re-tag), it's probably not going to be easy to add a
Release-x tag to a non-head revision :-(
Right... Who wants to write a new CI server? ;-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20111001/225b7154/attachment-0002.html>
More information about the Mercurial
mailing list