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

Mercurial Changelog should compare with previous build

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • mercurial-plugin
    • None

      Mercurial Changelog should compare with revision of the previous build instead of relying on local changes.
      When using multiple slaves, current implementation is taking in account changes which were already tested by a previous build on a different slave.
      Also, when a workspace is wiped out (or a new slave installed), changelog is empty since a full clone was needed.
      That wanted behavior is already implemented by other SCM plugins.

          [JENKINS-10255] Mercurial Changelog should compare with previous build

          Julien Carsique created issue -

          Jesse Glick added a comment -

          This was supposed to have been fixed long ago, with MercurialTagAction and PollingResult and so on. Perhaps it regressed, or is broken in particular cases?

          Jesse Glick added a comment - This was supposed to have been fixed long ago, with MercurialTagAction and PollingResult and so on. Perhaps it regressed, or is broken in particular cases?
          Jesse Glick made changes -
          Link New: This issue duplicates JENKINS-2180 [ JENKINS-2180 ]

          davidmc24 added a comment -

          I'm pretty sure that this issue has nothing to do with JENKINS-2180; removing the "duplicates" link.

          davidmc24 added a comment - I'm pretty sure that this issue has nothing to do with JENKINS-2180 ; removing the "duplicates" link.
          davidmc24 made changes -
          Link Original: This issue duplicates JENKINS-2180 [ JENKINS-2180 ]

          davidmc24 added a comment -

          I'll take a crack at resolving this issue. I've reproduced the behavior in a unit test, and think I have an approach for correcting it.

          davidmc24 added a comment - I'll take a crack at resolving this issue. I've reproduced the behavior in a unit test, and think I have an approach for correcting it.
          davidmc24 made changes -
          Assignee Original: Kohsuke Kawaguchi [ kohsuke ] New: davidmc24 [ davidmc24 ]

          davidmc24 added a comment -

          Sent pull request for my changes.

          https://github.com/jenkinsci/mercurial-plugin/pull/5

          davidmc24 added a comment - Sent pull request for my changes. https://github.com/jenkinsci/mercurial-plugin/pull/5

          David Santiago Turiño added a comment -

          This fix is a must have in order to be confident with Jenkins changes summaries when working with Mercurial.

          David Santiago Turiño added a comment - This fix is a must have in order to be confident with Jenkins changes summaries when working with Mercurial.

          SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: David M. Carr
          Path:
          src/test/java/hudson/plugins/mercurial/MercurialSCMTest.java
          http://jenkins-ci.org/commit/mercurial-plugin/d757d782fe075bf5831e1df81787a4977be53f57
          Log:
          JENKINS-10255 Touch up the tests I added for the changelog issues (which were applied as patches by willemv).

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: David M. Carr Path: src/test/java/hudson/plugins/mercurial/MercurialSCMTest.java http://jenkins-ci.org/commit/mercurial-plugin/d757d782fe075bf5831e1df81787a4977be53f57 Log: JENKINS-10255 Touch up the tests I added for the changelog issues (which were applied as patches by willemv).

            davidmc24 davidmc24
            jcarsique Julien Carsique
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: