1353835 - update release promotion to support Aurora-on-Beta shipping procedure

Status: RESOLVED FIXED

(Release Engineering :: Release Automation: Other, enhancement, P1)

Description

[[e-mail] (:bhearsum)]

As part of killing the Dawn project we're expecting to change the flow of updates on the Beta channel slightly. Starting with 55.0b1, we will be shipping early Betas to the former Aurora channel users first, and may not ship early Betas to the existing beta population at all.

We'll need to change the release automation configs to update the primary Aurora update rule when shipping any Betas or RCs.

We'll also need to find some way of _not_ automatically shipping early Betas to the existing Beta population. We may need a separate type "publish_rules" in the mozharness configs for this, and maybe another human decision task to trigger them?

Comment 1

[[e-mail] (:bhearsum)]

(In reply to Ben Hearsum (:bhearsum) from comment #0)
> We'll need to change the release automation configs to update the primary
> Aurora update rule when shipping any Betas or RCs.
> 
> We'll also need to find some way of _not_ automatically shipping early Betas
> to the existing Beta population. We may need a separate type "publish_rules"
> in the mozharness configs for this, and maybe another human decision task to
> trigger them?

There's still a chance we may not ship the existing Betas to Aurora users, but if we do I think we need the following changes to release promotion (haven't tested this - so there might be more, or different things needed):
- Add aurora to the channel list for Betas and Releases (https://hg.mozilla.org/mozilla-central/file/default/testing/mozharness/configs/releases/updates_firefox_beta.py and https://hg.mozilla.org/mozilla-central/file/default/testing/mozharness/configs/releases/updates_firefox_release.py)
- Change graph1 for beta to ship to the aurora channel (add it to https://github.com/mozilla-releng/build-buildbot-configs/blob/master/mozilla/config.py#L2218)
- Do something to make sure we don't automatically ship early Betas to the "beta" channel. This probably means pulling the beta channel publishing out of graph1, and add a graph2 that blocks on a human decision task. We might be able to tweak the release_channel_mapping regex (https://github.com/mozilla-releng/build-buildbot-configs/blob/master/mozilla/config.py#L2218) to make it still automatically ship for later Betas?
-- Change the release channel mapping regex 
- Add aurora to the list of channels to ship to in release graph 2 (https://github.com/mozilla/releasetasks/blob/master/releasetasks/release_configs/prod_mozilla-release_firefox_rc_graph_2.yml#L32)

If we end up giving Aurora users a repack or some other thing that's not the current Beta builds, we'll have to do something different.

Comment 2

[Rail Aliiev [:rail]]

assigning to myself to track it

Comment 3

[Rail Aliiev [:rail]]

this is pretty much done in various bugs.