canmove, Confirmed users
6,441
edits
ReleaseEngineering/Archive/Enable or Disable Updates on Aurora: Difference between revisions
ReleaseEngineering/Archive/Enable or Disable Updates on Aurora (view source)
Revision as of 13:28, 28 October 2014
, 28 October 2014no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Release Engineering How To|Enable or Disable Updates on Aurora}} | {{Release Engineering How To|Enable or Disable Updates on Aurora}} | ||
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. | 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. We're also occaisonly asked to disable updates temporarily for other reasons. This document describes how to do both of these things. | ||
Note the magic rule ids below. These correspond to ids of rows in the "rules" table of Balrog. If we fix {{bug|1067402}} we can pass more intelligable values here. | Note the magic rule ids below. These correspond to ids of rows in the "rules" table of Balrog. If we fix {{bug|1067402}} we can pass more intelligable values here. | ||
= Disabling Updates = | = Disabling Updates = | ||
NOTE: Disabling no longer has to be done by hand during uplifts. The uplift script does it. | |||
As cltbld@buildbot-master81: | As cltbld@buildbot-master81: | ||
<pre> | <pre> | ||