[
https://issues.jenkins-ci.org/browse/JENKINS-12048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159933#comment-159933
]
Cass Costello edited comment on JENKINS-12048 at 3/6/12 10:46 PM:
------------------------------------------------------------------
Still exists with Jenkins ver. 1.454 and HG plugin 1.38
Started on Mar 6, 2012 2:43:41 PM
[workspace] $ /usr/bin/hg pull --rev default
pulling from http://guest:***@f1tst-linbld100/cgi-bin/hgwebdir.cgi/RCALParent/
searching for changes
no changes found
[workspace] $ /usr/bin/hg log --style
/root/.jenkins/jobs/RCALParent/workspace/tmp1653283168161523774style --branch
default --no-merges --prune d192aa5a7ebca288cc92070b3e4e7f54578d99fb
hg log: option --branch not recognized
hg log [OPTION]... [FILE]
What's the best way for me to have a look at the code and request a merge?
was (Author: cass_costello):
Still exists with 1.452 and 1.38
Started on Mar 6, 2012 2:43:41 PM
[workspace] $ /usr/bin/hg pull --rev default
pulling from http://guest:***@f1tst-linbld100/cgi-bin/hgwebdir.cgi/RCALParent/
searching for changes
no changes found
[workspace] $ /usr/bin/hg log --style
/root/.jenkins/jobs/RCALParent/workspace/tmp1653283168161523774style --branch
default --no-merges --prune d192aa5a7ebca288cc92070b3e4e7f54578d99fb
hg log: option --branch not recognized
hg log [OPTION]... [FILE]
What's the best way for me to have a look at the code and request a merge?
> Wrong option "--branch" used by change polling
> -----------------------------------------------
>
> Key: JENKINS-12048
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12048
> Project: Jenkins
> Issue Type: Bug
> Components: mercurial
> Reporter: Christoph Neuroth
> Assignee: davidmc24
> Priority: Critical
>
> With Jenkins 1.442, Mercurial Plugin 1.38, the change polling issues a "hg
> log" command using "\-\-branch foo", which mercurial doesn't know about.
> Should be "\-b" or "\-\-only-branch".
--
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
