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

Support module filtering in MercurialChangeSetList

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • mercurial-plugin
    • None
    • Platform: All, OS: All

      Since the "module" is not considered in the MercurialChangeSetList, all
      changesets in the repository will be applied to buildjob i Hudson even if they
      are not affecting the module.
      The proposed patch (from 1.22 tag) filters changessets with no changes in the
      given module when parsing the changeset file.

        1. patch.txt
          37 kB
        2. patch.txt
          37 kB

          [JENKINS-4702] Support module filtering in MercurialChangeSetList

          sunfire added a comment -

          Created an attachment (id=961)
          Proposed patch

          sunfire added a comment - Created an attachment (id=961) Proposed patch

          sunfire added a comment -

          Created an attachment (id=962)
          The corrected version...

          sunfire added a comment - Created an attachment (id=962) The corrected version...

          Jesse Glick added a comment -

          I should probably be default owner of this subcomponent...

          Jesse Glick added a comment - I should probably be default owner of this subcomponent...

          Jesse Glick added a comment -

          Reporter - in the future please do not submit patches with unrelated changes to
          code, such as reformatting. This makes it nearly impossible to review what you
          are actually changing, thus what regressions your change might cause. A patch
          should be as short as possible to accomplish the desired change in behavior.

          Also patches without accompanying tests are less likely to be applied quickly.

          In this case it seems that the only actual change is to add
          filterChangesSetForModule and call it from the end of parse. I think I can take
          it from there.

          Jesse Glick added a comment - Reporter - in the future please do not submit patches with unrelated changes to code, such as reformatting. This makes it nearly impossible to review what you are actually changing, thus what regressions your change might cause. A patch should be as short as possible to accomplish the desired change in behavior. Also patches without accompanying tests are less likely to be applied quickly. In this case it seems that the only actual change is to add filterChangesSetForModule and call it from the end of parse. I think I can take it from there.

          SCM/JIRA link daemon added a comment -

          Code changed in hudson
          User: : jglick
          Path:
          trunk/hudson/plugins/mercurial/src/main/java/hudson/plugins/mercurial/MercurialChangeLogParser.java
          trunk/hudson/plugins/mercurial/src/main/java/hudson/plugins/mercurial/MercurialSCM.java
          trunk/hudson/plugins/mercurial/src/test/java/hudson/plugins/mercurial/MercurialSCMTest.java
          http://fisheye4.cenqua.com/changelog/hudson/?cs=23101
          Log:
          [FIXED JENKINS-4702] Omit changesets from changelog if a module list has been specified and they do not match.

          SCM/JIRA link daemon added a comment - Code changed in hudson User: : jglick Path: trunk/hudson/plugins/mercurial/src/main/java/hudson/plugins/mercurial/MercurialChangeLogParser.java trunk/hudson/plugins/mercurial/src/main/java/hudson/plugins/mercurial/MercurialSCM.java trunk/hudson/plugins/mercurial/src/test/java/hudson/plugins/mercurial/MercurialSCMTest.java http://fisheye4.cenqua.com/changelog/hudson/?cs=23101 Log: [FIXED JENKINS-4702] Omit changesets from changelog if a module list has been specified and they do not match.

            jglick Jesse Glick
            sunfire sunfire
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: