canmove, Confirmed users
6,439
edits
ReleaseEngineering/How To/Create new ESR branch: Difference between revisions
ReleaseEngineering/How To/Create new ESR branch (view source)
Revision as of 14:00, 26 February 2016
, 26 February 2016no edit summary
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
See {{bug|1237094}} and {{bug|1135702}} for the details and examples | See {{bug|1237094}} and {{bug|1135702}} for the details and examples | ||
== buildbot-configs changes == | == buildbot-configs changes == | ||
| Line 40: | Line 32: | ||
* update previous release configs to remove <tt>releaseConfig['bouncer_aliases']</tt>, and set | * update previous release configs to remove <tt>releaseConfig['bouncer_aliases']</tt>, and set | ||
releaseConfig['ftpSymlinkName'] = 'latest-10.0esr' | releaseConfig['ftpSymlinkName'] = 'latest-10.0esr' | ||
== tools changes == | |||
[https://bugzilla.mozilla.org/attachment.cgi?id=678767&action=edit tools changes] | |||
* adds new branch to buildapi's [http://hg.mozilla.org/build/tools/file/default/buildfarm/maintenance/production-branches.json production-branches.json] file | |||
* mozconfig whitelist changes (tested in {{bug|808077}}) | |||
* preproduction tweaks | |||
* since the [https://bugzilla.mozilla.org/attachment.cgi?id=678814&action=edit config patch] introduces new configuration file(s) which are needed to be symlinked on the build/scheduler masters there is a need for a fabric methods to create the links | |||
* adds new release branch to [http://hg.mozilla.org/build/tools/file/default/buildfarm/maintenance/production-masters.json production-masters.json] file | |||
It's important that the buildbot-configs changes are landed and in production prior to adding the symlinks and adjusting production-masters.json. When you land these two changes you must immediately run the fabric method to put the symlinks in place to ensure the masters will continue to function correctly. | |||
= External changes = | = External changes = | ||