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

Wacky number for changes in build using Mercurial plugin

      It just shows random numbers for the changeset ids.

      This sounds like the same type of problem as JENKINS-7154, except I'm not using git. I'm using muti-scms with mercurial, so I'm not sure where the problem lies.

          [JENKINS-14365] Wacky number for changes in build using Mercurial plugin

          David Watson created issue -

          Jesse Glick added a comment -

          Odd. Probably a bug in multiple-scms. For example, http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/9339/changes shows changes 1-10 but the #9339 section of http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/changes shows 93, 94, 740, 741, 43638, 43639, 43640, 43641, 529, and 1!

          Jesse Glick added a comment - Odd. Probably a bug in multiple-scms. For example, http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/9339/changes shows changes 1-10 but the #9339 section of http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/changes shows 93, 94, 740, 741, 43638, 43639, 43640, 43641, 529, and 1!

          Jesse Glick added a comment -

          Visible at http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/changes for example: third item in build #9339 is displayed as "740. Performance: ..." because HTML has <li value="0740d2a6bcb311de7531ef4c9f4e3838274b990f">Performance: ..." which is wrong.

          Jesse Glick added a comment - Visible at http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/changes for example: third item in build #9339 is displayed as "740. Performance: ..." because HTML has <li value="0740d2a6bcb311de7531ef4c9f4e3838274b990f">Performance: ..." which is wrong.
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Jesse Glick added a comment -

          Trying to add cause in a comment, but failing so far...

          Jesse Glick added a comment - Trying to add cause in a comment, but failing so far...

          Jesse Glick added a comment -

          <li value="0740d2a6bcb311de7531ef4c9f4e3838274b990f"> for example at http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/changes shows as item #740.

          Jesse Glick added a comment - <li value="0740d2a6bcb311de7531ef4c9f4e3838274b990f"> for example at http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/changes shows as item #740.

          Jesse Glick added a comment - - edited

          In fact reproducible without multiple-scms plugin, just on a plain job using Mercurial. The problem is in jenkins/core/src/main/resources/hudson/scm/SCM/project-changes.jelly which uses <li value="${c.revision}"> even though no getRevision method is defined in the core ChangeLogSet.Entry (MercurialChangeSet happens to define it without overriding).

          Jesse Glick added a comment - - edited In fact reproducible without multiple-scms plugin, just on a plain job using Mercurial. The problem is in jenkins/core/src/main/resources/hudson/scm/SCM/project-changes.jelly which uses <li value="${c.revision}"> even though no getRevision method is defined in the core ChangeLogSet.Entry ( MercurialChangeSet happens to define it without overriding).
          Jesse Glick made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: multiple-scms [ 15810 ]
          Priority Original: Major [ 3 ] New: Minor [ 4 ]
          Summary Original: Wacky number for changes in build using multiscm/hg New: Wacky number for changes in build using Mercurial plugin
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-7154 [ JENKINS-7154 ]

          Jesse Glick added a comment -

          JENKINS-7154 worked around this problem by adding a custom GitSCM/project-changes.jelly, but that just begs the question of why the default page has code which does nothing for an SCM which does not happen to provide a method named getRevision, and does something clearly wrong for an SCM which does.

          Jesse Glick added a comment - JENKINS-7154 worked around this problem by adding a custom GitSCM/project-changes.jelly , but that just begs the question of why the default page has code which does nothing for an SCM which does not happen to provide a method named getRevision , and does something clearly wrong for an SCM which does.

            jglick Jesse Glick
            dwatson David Watson
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: