#438: Mercurial does not update to the right revision when building a tag from a
named branch
----------------------+------------------------
Reporter: cdevienne | Owner:
Type: defect | Status: reopened
Priority: major | Milestone: undecided
Version: 0.8.5 | Resolution:
Keywords: |
----------------------+------------------------
Comment (by marcusl):
Yes, just omitting the rev will work, which is what the OP said too.
* A revision string will either be an int, a 12-char hex, or a 40-char
hex.
* Branch names could be anything though, so that's trickier.
One could, of course, run 'hg tags' or 'hg branches' against the remote
repo and see if it's included in the result.
I agree with the growing pains thing. I think we should really look at
repo-caching on the slave(s), in order to reduce this (something I wanted
to do with SVN too, btw), or just wait for
http://mercurial.selenic.com/wiki/ShallowClone to be done. :)
--
Ticket URL: <http://trac.buildbot.net/ticket/438#comment:8>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
