[JIRA] [mercurial-plugin] (JENKINS-28526) Build emails reference unrelated changesets
Title: Message Title fragpit fragpit updated an issue Jenkins / JENKINS-28526 Build emails reference unrelated changesets Change By: fragpit fragpit Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-28526) Build emails reference unrelated changesets
Title: Message Title Gedalia Pasternak commented on JENKINS-28526 Re: Build emails reference unrelated changesets I think this fixes if if someone could merge it in that would be really helpful... https://github.com/jenkinsci/mercurial-plugin/pull/73/files Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-28526) Build emails reference unrelated changesets
Title: Message Title Kent Johnson created an issue Jenkins / JENKINS-28526 Build emails reference unrelated changesets Issue Type: Bug Assignee: Jesse Glick Components: mercurial-plugin Created: 21/May/15 2:44 PM Environment: Jenkins 1.614, mercurial-plugin 1.52, mercurial 3.4, Windows 64 Priority: Minor Reporter: Kent Johnson Mercurial 3.4 changed the behavior of the log command as used by this plugin. A command such as hg log --rev default:0 --follow --prune 5029 now will show unrelated changesets on other branches (specifically the head of an active branch other than default). This results in build logs and emails that show unrelated changesets and build emails being sent to the authors of unrelated changesets. AFAICT the mercurial changeset is http://hg.intevation.org/mercurial/crew/rev/c260887cdbcd. There is related discussion here: http://thread.gmane.org/gmane.comp.version-control.mercurial.general/36471. I'm not sure why the hg log behaviour changed or even if it is correct, but from the discussion it seems like the command used by this plugin is not correct either. The --follow flag is used to follow changes to a particular file, not to follow the ancestor relationships of changesets. A better command seems to be hg log --rev descendents(5029)::default which directly asks for all the ch