canmove, Confirmed users
6,439
edits
Release:Release Automation on Mercurial:Updates through Shipping: Difference between revisions
Release:Release Automation on Mercurial:Updates through Shipping (view source)
Revision as of 16:03, 8 March 2016
, 8 March 2016→Betas/Final Releases
m (→Betas/Final Releases: be bolder) |
|||
| Line 156: | Line 156: | ||
'''These instructions cover _typical_ cases. If any special requirements have been requested (ie, whatsnew page) you may need to do different or additional things at the same time.'''<br/> | '''These instructions cover _typical_ cases. If any special requirements have been requested (ie, whatsnew page) you may need to do different or additional things at the same time.'''<br/> | ||
We have a builder that updates the right parts of Balrog to push a release live. When instructed, you can use "force build" to start it. | Before publishing, you should verify that the throttle rate is set as expected - automation will not update this for you. Compare the rate in the push e-mail (eg: 25% or 100%) to the rate on [https://aus4-admin.mozilla.org/rules the Balrog admin interface]. More on throttle rates can be found in the [[#Throttling | Throttling section of this page]] | ||
We have a builder that updates the right parts of Balrog to push a release live. When instructed, you can use "force build" to start it. | |||
'''NOTE:''' this step requires a "double authorization" - appropriate sign off by QE or RelMan, ''and'' verifying that automation is ready (e.g. 'ready to ship' notification). | '''NOTE:''' this step requires a "double authorization" - appropriate sign off by QE or RelMan, ''and'' verifying that automation is ready (e.g. 'ready to ship' notification). | ||