977
edits
ReleaseEngineering/TryserverAsBranch: Difference between revisions
Jump to navigation
Jump to search
→Dry run with tryserver slaves from production pool
Lukasblakk (talk | contribs) |
Lukasblakk (talk | contribs) |
||
| Line 18: | Line 18: | ||
* Make sure .ssh is 700 and key is 600 in order to connect to stage | * Make sure .ssh is 700 and key is 600 in order to connect to stage | ||
* Put in patch to fix tryserver post_upload path/dir to stage instead of build.m.o | * Put in patch to fix tryserver post_upload path/dir to stage instead of build.m.o | ||
==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 | |||
* 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 | |||
* They will be attached to the new try-as-branch master | |||
* The master will run in parallel with the current try, until green | |||
* Then turn on email notification and switch the tinderbox url to MozillaTry | |||
* At the same time turn off all but mobile on old try | |||
* Re-image the rest of the slaves and put in build network | |||
==Update Nagios== | ==Update Nagios== | ||