1429283 - Stop updating existing linux/mac bz2 watershed rules from automation and use 57.0.4 as permanent watershed

Status: RESOLVED FIXED

(Release Engineering :: Release Requests, enhancement)

Description

[Jordan Lund (:jlund)]

context: we want to keep 57.0.4 as a permanent watershed: https://docs.google.com/spreadsheets/d/1XQcYQg2UuVloQWnETfqxbsqXfUBRhkq2aUB8MTp3Y3s/edit?ts=5a5510cb#gid=0

I was going to add a rule because Taskcluster in-tree releases, which do not know about bz2 updates, won't be enabled until 59. Nick had a better idea: update existing releasetasks based automation and disable bz2 compression update creation.


Should be as simple as setting: https://hg.mozilla.org/build/buildbot-configs/file/default/mozilla/config.py#l2165

So that we don't update balrog rules: https://dxr.mozilla.org/build-central/source/releasetasks/releasetasks/templates/desktop/publish_balrog.yml.tmpl#36

This can be done anytime before we gtb on 58.0 I believe.

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

Attachment: [buildbot-configs] Disable lzma_to_bz2 on mozilla-release, birch, and maple

Comment 2

[Jordan Lund (:jlund)]

Comment on attachment 8942011 [details] [diff] [review]
[buildbot-configs] Disable lzma_to_bz2 on mozilla-release, birch, and maple

ah, good call with project branches based on m-r.

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

Comment on attachment 8942011 [details] [diff] [review]
[buildbot-configs] Disable lzma_to_bz2 on mozilla-release, birch, and maple

https://hg.mozilla.org/build/buildbot-configs/rev/7eae33e5a71209affd70912be8d2b18205b829ba
https://hg.mozilla.org/build/buildbot-configs/rev/2b3d49a8a52a63a575d5a0e8a378eaf9db2eba95

Comment 4

[Nick Thomas [:nthomas] (UTC+12)]

The rules look fine as is, that is 680, 679, and 624 on release. At some point we could shuffle all the priorities up a bit (to make more space near the 90s).