[
https://issues.jenkins-ci.org/browse/JENKINS-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jglick closed JENKINS-13292.
----------------------------
Resolution: Duplicate
Using tag names in the "branch" field was never tested or supported. If it
happened to work in some versions of the plugin, it was by accident.
> Problem to update to a tagged revision
> --------------------------------------
>
> Key: JENKINS-13292
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13292
> Project: Jenkins
> Issue Type: Bug
> Components: mercurial
> Affects Versions: current
> Reporter: Helen Her
> Assignee: Kohsuke Kawaguchi
>
> In the previous version we were able to clone the remote repository and
> update it to a tagged revision
> as you can see the log here, v4.6.0.118 it's the tag of the branch r4.6.0.118
> $ hg clone --rev v4.6.0.118 remote_repository_url local_repository
> adding changesets
> adding manifests
> adding file changes
> added 199 changesets with 13401 changes to 6466 files
> updating to branch r4.6.0.118
> But when we updated the plugin to the version 1.38, we couldn't clone the
> remote repository and update it to a tagged revision
> $ hg clone --rev v4.6.0.118 --noupdate remote_repository_url local_repository
> adding changesets
> adding manifests
> adding file changes
> added 199 changesets with 13401 changes to 6466 files
> [v4.6.0.118] $ hg update --rev v4.6.0.118
> abort: unknown revision 'v4.6.0.118'!
> So we had to downgrade the mercurial plugin to 1.37 for the time being.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
