1816164 - prep_repo.sh should also check the target branch-heads/xxx commits for no-op commits

Status: RESOLVED FIXED

(Core :: WebRTC, task, P2)

Description

[Michael Froman [:mjf]]

Unexpectedly, we can see commits cherry-picked into multiple chromium milestone branch-heads. Originally, I expected things cherry-picked in the milestone branch-head would be absorbed during the next fast-forward update. In other words, that the cherry-picked patches would be patches from the next release. However, while running the v108 it we see that changes cherry-picked for the v107 release needed to be cherry-picked for the v108 release as well.

The prep_repo.sh script should add no-op tracking files for the target branch-head cherry-pick commits as well.

Comment 1

[Michael Froman [:mjf]]

Because of the added complexity here, and the reality that prepping the repo is conceptually different than building the no-op commit data, I'm going to separate this out into a separate script.

Comment 2

[Michael Froman [:mjf]]

Attachment: Bug 1816164 - pt1 - remove no-op commit processing from prep_repo.sh r?ng!

Comment 3

[Michael Froman [:mjf]]

Attachment: Bug 1816164 - pt2 - add new build_no_op_commits.sh r?ng!

Depends on D170265

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/2ed27c565214
pt1 - remove no-op commit processing from prep_repo.sh r=ng DONTBUILD
https://hg.mozilla.org/integration/autoland/rev/bfe771f7165e
pt2 - add new build_no_op_commits.sh r=ng DONTBUILD

Comment 5

[Sandor Molnar[:smolnar]]

https://hg.mozilla.org/mozilla-central/rev/2ed27c565214
https://hg.mozilla.org/mozilla-central/rev/bfe771f7165e