-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
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.
- duplicates
-
JENKINS-49897 gerrit-plugin pr branch names are incorrectly name
-
- Open
-
- is duplicated by
-
JENKINS-68014 One "change" per change instead of per patch set
-
- Closed
-
- is related to
-
JENKINS-58958 Use the same Jenkins workspace on a Change basis
-
- Open
-
[JENKINS-62816] Group patchsets into a single change
Attachment | New: image-2020-08-06-22-26-49-905.png [ 52134 ] |
Attachment | New: image-2020-08-14-11-34-29-473.png [ 52208 ] |
Attachment | New: image-2020-08-14-11-36-06-169.png [ 52209 ] |
Attachment | New: image-2020-08-14-14-43-41-459.png [ 52210 ] |
Link | New: This issue duplicates JENKINS-49897 [ JENKINS-49897 ] |
Link | New: This issue is related to JENKINS-58958 [ JENKINS-58958 ] |
Link |
New:
This issue is duplicated by |