[JIRA] [mercurial-plugin] (JENKINS-29879) mercurial branch change log includes every change
Title: Message Title Gedalia Pasternak commented on JENKINS-29879 Re: mercurial branch change log includes every change we are using the multiple scms plugin. Which seems to produce less then ideal change info (hash keys are listed but not clearly associate with a repo in the UI). I'm wondering where the :0 argument is coming from since removing that on the command line seems to do the right thing. 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-29879) mercurial branch change log includes every change
Title: Message Title Gedalia Pasternak edited a comment on JENKINS-29879 Re: mercurial branch change log includes every change weareusingthemultiplescmsplugin.Whichseemstoproducelessthenidealchangeinfo(hashkeysarelistedbutnotclearly associate associated witharepointheUI).I'mwonderingwherethe:0argumentiscomingfromsinceremovingthatonthecommandlineseemstodotherightthing. 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-29879) mercurial branch change log includes every change
Title: Message Title Gedalia Pasternak commented on JENKINS-29879 Re: mercurial branch change log includes every change there's a good chance it's the same as https://issues.jenkins-ci.org/browse/JENKINS-28526 since we're using 3.4+ and it spontaneously started when we upgraded versions 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-29879) mercurial branch change log includes every change
Title: Message Title Jesse Glick resolved as Incomplete Cannot diagnose without a way to reproduce from scratch. The --prune option is supposed to be truncating the log at the revision checked out by the previous build, leaving you with the commits in this build. If you are using the Multiple SCMs plugin, that is possibly involved. Jenkins / JENKINS-29879 mercurial branch change log includes every change Change By: Jesse Glick Status: Open Resolved Resolution: Incomplete 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-29879) mercurial branch change log includes every change
Title: Message Title Gedalia Pasternak created an issue Jenkins / JENKINS-29879 mercurial branch change log includes every change Issue Type: Bug Assignee: Jesse Glick Components: mercurial-plugin, multiple-scms-plugin Created: 10/Aug/15 4:16 PM Environment: Mercurial plugin 1.54 jenkins 1.624 Mercurial 3.5 (seems to happen on older versions as well) Labels: changelog scm mercurial Priority: Major Reporter: Gedalia Pasternak the hg change log that is generated from: hg log --rev branch_name:0 --follow --prune hash_name includes every commit in a repository for me, I've tested this on 3-4 repos with a few different version of hg. it seems to produce the right info with: hg log --rev branch_name --follow --prune hash_name not sure if a problem is that branch name = diguy-13_0-ecosim (but diguy-13_0-ecosim:0 doesn't behave any differently
