[
https://issues.jenkins-ci.org/browse/JENKINS-13842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163334#comment-163334
]
jglick commented on JENKINS-13842:
----------------------------------
A test case would be something like a bundle repo (or a set of Hg commands to
create an equivalent repo starting with hg init), plus the SCM snippet from a
job config.xml - whatever concrete instructions are needed to reproduce the
issue from scratch. (A unit test is of course ideal but more work to prepare if
you have not played with the sources.)
Regarding Mercurial versions, my own organization runs 1.3.1 on some servers
due to a serious regression in the merge algorithm in 1.4. General policy for
the plugin is that it should work on 1.0+ unless there is a compelling need to
require a newer version; certain optional features are conditionally enabled
based on version, such as hg relink.
> Mercurial poll triggers build due to unrelated changes
> ------------------------------------------------------
>
> Key: JENKINS-13842
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13842
> Project: Jenkins
> Issue Type: Bug
> Components: mercurial
> Affects Versions: current
> Reporter: Thomas Lotze
> Assignee: Kohsuke Kawaguchi
>
> The current Mercurial poll command is formulated such that it may falsely
> detect new changes if there have ever been any branches with the same name as
> that relevant to the build, but which are not ancestors of the current
> working-directory revision in terms of the revision DAG.
> If the repository happens to contain another branch with the same name,
> Jenkins will continuously build the project and the only way to stop it is to
> push a dummy merge of that other branch into the line of development Jenkins
> is supposed to build.
> A better way to ask for new descendants of the current working-directory
> revision would be this:
> hg log --branch $branch --rev "descendants(children($revision))"
> The children predicate is needed because descendants always include the named
> revision itself.
--
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
