ReleaseEngineering/Archive/Adjust B2G Update Channels on Merge Day
From MozillaWiki
< ReleaseEngineering(Redirected from ReleaseEngineering/How To/Adjust B2G Update Channels on Merge Day)
This page is obsolete
When Nightly merges into Aurora every 6 weeks we lock Aurora updates at a specific old version for a period of time (days to a week) while QA runs some tests. Once their tests have passed, we re-enable updates. This document describes how to do both of these things.
Central will become an odd-numbered Gecko version
- Repoint B2G Aurora updates at Aurora builds:
- Go to the Balrog Admin interface's rules page.
- Find the rule that has "B2G" for the product and "aurora" for the channel
- Change the "Mapping" for that rule to "B2G-mozilla-aurora-nightly-latest"
- Scroll to the right and click "Update" to make the change.
Central will become an even-numbered Gecko version
- Point B2G Aurora updates at the newly created mozilla-b2gXX builds:
- Go to the Balrog Admin interface's rules page.
- Find the rule that has "B2G" for the product and "aurora" for the channel
- Change the "Mapping" for that rule to "B2G-mozilla-b2gXX_vX_X-nightly-latest" - for example, "B2G-mozilla-b2g32_v2_0-nightly-latest" was used on the merge day that created the mozilla-b2g32_v2_0 branch.
- Scroll to the right and click "Update" to make the change.