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

          Connor Newton created issue -
          Connor Newton made changes -
          Description Original: Every patch set being reported as a distinct change *surely* must not be the intended behaviour?

          !gerrit-multibranch.png|width=569,height=707!

          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.           		New: Every patch set being reported as a distinct change *surely* must not be the intended behaviour?

          !gerrit-multibranch-1.png|width=431,height=539,thumbnail!

          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.
          Joe Hansche made changes -
          Link New: This issue duplicates JENKINS-62816 [ JENKINS-62816 ]
          Joe Hansche made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

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

              Created:
              Updated:
              Resolved: