[
https://issues.jenkins-ci.org/browse/JENKINS-13842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163322#comment-163322
]
Thomas Lotze commented on JENKINS-13842:
----------------------------------------
What would a test case for this look like? A repository with a description of
which revisions to push to another repository visible to a Jenkins instance at
what point? Some Jenkins configuration? I'm not sure that would end up more
concise than the short description I gave already, but I can try when I know
what you'd like to see.
OTOH, I don't understand that comment about the mercurial version. Which
versions of mercurial are you committed to support? Revsets have been part of
mercurial since version 1.5 or 1.6 - do you need to support versions as old as
that by new Jenkins releases?
> 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
