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

Plugin does not work with Mercurial 3.4.2

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      We recently upgraded to mercurial 3.4.2 on our masters and slaves. Now when you try and build a project with the mercurial scm enabled we get this error, when the changelog is being computed.

      I've attached the console log, and it seems that the --follow flag is the culprit when hg log is run.

      Downgrading to Mercurial 3.3.3 fixes the issues.

        Attachments

          Issue Links

            Activity

            Hide
            krandell Kim Randell added a comment -

            Oh, I've just noticed that xavierzwirtz has already created a pull request with a fix for this. Linked it now.

            Show
            krandell Kim Randell added a comment - Oh, I've just noticed that xavierzwirtz has already created a pull request with a fix for this. Linked it now.
            Hide
            krandell Kim Randell added a comment -

            There appears to be problem with Mercurial 3.4 even when the log command executes successfully. We are finding that the command returns a number of unwanted changesets (in our case ~2000 of them), apparently everything which is not an ancestor of the current branch head.

            I tested this command manually and found that it returns the expected result for 3.3.3 and the extra results for 3.4 (and 3.6):
            hg log --rev <branch_name>:0 --follow --prune <last_changeset>

            The following command returns the desired results on 3.3.3, 3.4, and 3.6
            hg log --rev "ancestors('<branch_name>')" --prune <last_changeset>
            The single quotes around <branch_name> also fix the whitespace problem.

            This is due to the following change:
            https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_3.4_.282015-05-01.29

            log: make -fr show complete history from the given revs

            https://selenic.com/pipermail/mercurial-devel/2015-March/066770.html

            Show
            krandell Kim Randell added a comment - There appears to be problem with Mercurial 3.4 even when the log command executes successfully. We are finding that the command returns a number of unwanted changesets (in our case ~2000 of them), apparently everything which is not an ancestor of the current branch head. I tested this command manually and found that it returns the expected result for 3.3.3 and the extra results for 3.4 (and 3.6): hg log --rev <branch_name>:0 --follow --prune <last_changeset> The following command returns the desired results on 3.3.3, 3.4, and 3.6 hg log --rev "ancestors('<branch_name>')" --prune <last_changeset> The single quotes around <branch_name> also fix the whitespace problem. This is due to the following change: https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_3.4_.282015-05-01.29 log: make -fr show complete history from the given revs https://selenic.com/pipermail/mercurial-devel/2015-March/066770.html
            Hide
            jglick Jesse Glick added a comment -

            I think it is rather the spaces in the branch name. If you must use them, downgrade Mercurial for the moment. There is a proposed fix but no current proposal for automated testing.

            Show
            jglick Jesse Glick added a comment - I think it is rather the spaces in the branch name. If you must use them, downgrade Mercurial for the moment. There is a proposed fix but no current proposal for automated testing.

              People

              • Assignee:
                jglick Jesse Glick
                Reporter:
                madsnielsen Mads Nielsen
              • Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: