977
edits
ReleaseEngineering/TryserverAsBranch: Difference between revisions
Jump to navigation
Jump to search
→Rollout process
Lukasblakk (talk | contribs) |
Lukasblakk (talk | contribs) |
||
| Line 21: | Line 21: | ||
==Rollout process== | ==Rollout process== | ||
* Notify dev-planning, dev-tree-management, blog, put up a notice on MozillaTry tinderbox to let people know there will be longer wait times in the transition period | * Notify dev-planning, dev-tree-management, blog, put up a notice on MozillaTry tinderbox to let people know there will be longer wait times in the transition period | ||
* Blog/Update docs about how to use push-to-try and the custom mozconfig option | * Blog/Update docs about how to use push-to-try and the custom mozconfig option | ||
* We will take 1/2 the slaves from the current try master and get them re-imaged and moved to build network | * We will take 1/2 the slaves from the current try master and get them re-imaged and moved to build network | ||
** make sure all machines have only trybld keys | |||
** ssh to build.m.o and stage.m.o with keys and accept host | |||
** firewall needs opening for sending to talos-master02.build | |||
* They will be attached to the new try-as-branch master | * They will be attached to the new try-as-branch master | ||
* The master will run in parallel with the current try, until green | * The master will run in parallel with the current try, until green | ||