Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-29879

mercurial branch change log includes every change

    Details

    • Similar Issues:

      Description

      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

        Attachments

          Issue Links

            Activity

            Hide
            jglick Jesse Glick added a comment -

            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.

            Show
            jglick Jesse Glick added a comment - 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.
            Hide
            gedalia Gedalia Pasternak added a comment - - edited

            we are using the multiple scms plugin. Which seems to produce less then ideal change info (hash keys are listed but not clearly associated 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.

            Show
            gedalia Gedalia Pasternak added a comment - - edited we are using the multiple scms plugin. Which seems to produce less then ideal change info (hash keys are listed but not clearly associated 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.
            Hide
            gedalia Gedalia Pasternak added a comment -

            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

            Show
            gedalia Gedalia Pasternak added a comment - 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

              People

              • Assignee:
                jglick Jesse Glick
                Reporter:
                gedalia Gedalia Pasternak
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: