Closed Bug 1159860 Opened 9 years ago Closed 9 years ago

Stop generating parent diffs for every commit

Categories

(MozReview Graveyard :: General, defect)

Development/Staging
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: smacleod, Assigned: smacleod)

Details

Attachments

(2 files, 1 obsolete file)

Currently for each commit after the base commit we generate two diffs and upload them to Review Board - a "diff" and a "parent diff". Review Board first applies the parent diff to give us the base for the commit, and then the diff is displayed on top of that.

Each of these commit review requests all point at the same base revision, and then include in their parent diff all commits that come before them in the push. This causes the parent diff to be larger for each successive commit.

The reason this was done is so that Review Board could point at the mainline repository (such as a mozilla-central). The mainline doesn't know of the commits up for review meaning Review Board could not use a non-mainline commit as the base for a commit review request.

In practice we've been pointing Review Board at the review repos themselves rather than the mainline meaning all these parent diffs are wasting space (and CPU resources being applied).

We should stop generating and uploading these parent diffs, instead just providing the proper base commit and a single diff for each commit. This also means mandating that Review Board must remain pointed at the review repo and not mainline going forward.
/r/8179 - MozReview: Allow specifying base_commit_id and make parent_diff optional (Bug 1159860). r?gps
/r/8181 - MozReview: Stop generating parent diffs (Bug 1159860); r?gps

Pull down these commits:

hg pull -r 158efe0c2b26977522c4803007414de0b95b4a74 https://reviewboard-hg.mozilla.org/version-control-tools/
Attachment #8601762 - Flags: review?(gps)
Comment on attachment 8601762 [details]
MozReview Request: bz://1159860/smacleod

https://reviewboard.mozilla.org/r/8177/#review6947

This all seems sensible to me given what we talked about last week and what's said in the commit messages.

Let's be sure to test this on dev before it is pushed to prod. I have a nice long commit series we can use to benchmark this. I'm excited about the reduced computation at push time! I'm already a bit concerned about push performance and it's good to see us going in the right direction.
Attachment #8601762 - Flags: review?(gps) → review+
Pushed https://hg.mozilla.org/hgcustom/version-control-tools/rev/bbf29965c039
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Attachment #8601762 - Attachment is obsolete: true
Attachment #8620190 - Flags: review+
Attachment #8620191 - Flags: review+
Product: Developer Services → MozReview
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: