[
https://issues.jenkins-ci.org/browse/JENKINS-13842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163076#comment-163076
]
jglick commented on JENKINS-13842:
----------------------------------
A self-contained reproducible test case is worth a thousand words.
Using revsets is probably not feasible since they will not work on older
versions of Mercurial. It would be possible to check the Hg version and switch
behavior, but this makes testing ineffective.
> 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
