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

One "change" per change instead of per patch set

XMLWordPrintable

      Every patch set being reported as a distinct change surely must not be the intended behaviour?

      I would have expected the desired behaviour would be for all builds for one change (above this would be 03/3) to be grouped rather than invalidating the "change" for the previous patch set and creating a brand new one.

      This way there will only ever be one build per "change"- that doesn't seem correct to me.

      Apologies if this is already configurable and I've managed to miss it in the settings or documentation - I swear I can't see anything relevant anywhere.

        1. gerrit-multibranch-1.png
          gerrit-multibranch-1.png
          105 kB

          [JENKINS-68014] One "change" per change instead of per patch set

          Joe Hansche added a comment - - edited

          Work for this was started in JENKINS-62816 but fell off my radar and the work was never picked back up.

          To answer the OP question: yes this was intended behavior as written (see discussion in the duplicate ticket). I happen to agree with you, that one "branch" per gerrit change makes the most sense, and happens to remain in line with the way that Github Pull Requests are organized. Also lets you see the build history as new patchsets are uploaded. Orphaning an old patchset branch and starting a brand new one every time the change is updated loses some valuable relevant history.

          Joe Hansche added a comment - - edited Work for this was started in JENKINS-62816 but fell off my radar and the work was never picked back up. To answer the OP question: yes this was intended behavior as written (see discussion in the duplicate ticket). I happen to agree with you, that one "branch" per gerrit change makes the most sense, and happens to remain in line with the way that Github Pull Requests are organized. Also lets you see the build history as new patchsets are uploaded. Orphaning an old patchset branch and starting a brand new one every time the change is updated loses some valuable relevant history.

            lucamilanesio Luca Domenico Milanesio
            phyrwork Connor Newton
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: