ReleaseEngineering:ProjectBranchPlanning: Difference between revisions

Jump to navigation Jump to search
Line 39: Line 39:
* 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
** Example customization is turning on nightly updates, if this comes up you can copy the process from the UX branch see [https://bugzilla.mozilla.org/attachment.cgi?id=531789 example patch] for what is required wrt AUS, once you've enabled nightlies you need to land in cvs, tag and then file a ServerOps bug ([https://bugzilla.mozilla.org/show_bug.cgi?id=657008 example])
** Example customization is turning on nightly updates, if this comes up you can copy the process from the UX branch see [https://bugzilla.mozilla.org/attachment.cgi?id=531789 example patch] for what is required wrt AUS, once you've enabled nightlies you need to land in cvs, tag and then file a ServerOps bug ([https://bugzilla.mozilla.org/show_bug.cgi?id=657008 example])
** There is a Mac specific issue caused by publishing snippets to a Darwin_x86_64-gcc3 directory, and the clients querying using different build targets so you should use the templates nthomas set up:
** If you do enable custom nightly channels for a project branch there is a Mac specific issue caused by publishing snippets to a Darwin_x86_64-gcc3 directory, and the clients querying using different build targets so you should use the templates nthomas set up:
  # ffxbld@aus2-staging
  # ffxbld@aus2-staging
  $ rsync -av ~/template/ /opt/aus2/incoming/2/Firefox/<new_branch_name>/
  $ rsync -av ~/template/ /opt/aus2/incoming/2/Firefox/<new_branch_name>/
Confirmed users
4,467

edits

Navigation menu