canmove, Confirmed users
1,126
edits
ReleaseEngineering:ProjectBranchPlanning: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering:ProjectBranchPlanning (view source)
Revision as of 17:38, 21 December 2014
, 21 December 2014Bug 1082602
(Bug 1082602) |
|||
| Line 35: | Line 35: | ||
* File a ServerOps bug to create repo in hg.m.o if repo does not already exist. Repos should be created under "/projects", "/services" or "/releases" whenever possible. | * File a ServerOps bug to create repo in hg.m.o if repo does not already exist. Repos should be created under "/projects", "/services" or "/releases" whenever possible. | ||
* | * File a [https://bugzilla.mozilla.org/enter_bug.cgi?product=Tree%20Management&component=Treeherder%3A%20Data%20Ingestion Treeherder bug] to get the repo added to Treeherder. | ||
* Create patches in buildbot-configs/mozilla/project_branches adding the project and if needed any custom mozconfig path or custom repo path | * Create patches in buildbot-configs/mozilla/project_branches adding the project and if needed any custom mozconfig path or custom repo path | ||
** By default, the project branches use the generic mozconfigs (in buildbot-configs/mozilla2/$platform), if you need custom mozconfigs you should create them across the board as we would prefer at this time to not have a mix of files and symlinks. You can override the 'mozconfig_dir' in the project_branches.py file | ** By default, the project branches use the generic mozconfigs (in buildbot-configs/mozilla2/$platform), if you need custom mozconfigs you should create them across the board as we would prefer at this time to not have a mix of files and symlinks. You can override the 'mozconfig_dir' in the project_branches.py file | ||