-
Bug
-
Resolution: Unresolved
-
Major
-
None
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.
[JENKINS-13842] Mercurial poll triggers build due to unrelated changes
Assignee | Original: Kohsuke Kawaguchi [ kohsuke ] | New: Jesse Glick [ jglick ] |
Workflow | Original: JNJira [ 144310 ] | New: JNJira + In-Review [ 176121 ] |