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

Group patchsets into a single change

XMLWordPrintable

      Instead of having a new "Change Request" in Multibranch Pipeline for every new patchset, it would be better to have just a single entry for the change, and new patchsets creating new builds into that already created "Change Request".

      This way, we would be able to check the entire build history for a change request (currently every new patchset causes the old one to get discarded) and even check the Git diffs between the different patchsets, and most importantly: the arrangement.

        1. image-2020-08-06-22-26-49-905.png
          image-2020-08-06-22-26-49-905.png
          58 kB
        2. image-2020-08-14-11-34-29-473.png
          image-2020-08-14-11-34-29-473.png
          23 kB
        3. image-2020-08-14-11-36-06-169.png
          image-2020-08-14-11-36-06-169.png
          92 kB
        4. image-2020-08-14-14-43-41-459.png
          image-2020-08-14-14-43-41-459.png
          49 kB

            lucamilanesio Luca Domenico Milanesio
            felipecassiors Felipe Santos
            Votes:
            5 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: