ReleaseEngineering/DisposableProjectRepositories

What is a disposable project branch?

These are project branches that can be cloned fresh from any mozilla-central based repo with the full gamut of tests enabled. No l10n or nightlies for now. Similar to TryServer but for longer, and just for you. Unlike Try, the commit level on these branches is level_2 (and above) contributors only so please bear that in mind.

Do you need a disposable branch?

Ask yourself the following:

Does your project have an end date?

If your answer is No then you should follow the process at Project Branch Planning

If your project is a temporary feature sprint that needs its own rapid test coverage but will eventually be merged into mozilla-central and no longer be on its own by all means, please go ahead and

Book one of our fabulous "disposable" project branches

• Sign up below in the BOOKING SCHEDULE
• Make a request to IT to reset the repo for you as a clone from your own project repo (or default mozilla-central:tip). Copy the script below into bug request, replacing the REPO_PATH and TWIG with your repo and booked branch.

export REPO_PATH=[path to your repo]                 # eg: users/lsblakk_mozilla.com/staging
export TWIG=[alder|birch|cedar|holly|larch|maple]    # whichever twig you booked

cd /repo/hg/scripts/
./reset_pp_repo.sh -s /repo/hg/mozilla/$REPO_PATH -r tip -d $TWIG

• Sit back and watch your builds and test results roll in (Alder,Birch,Cedar,Holly,Larch,Maple).
  • Special note - READ ME: the first push to your newly cloned repo should now trigger a build since bug 562026 was checked in. If it does not, please re-open the bug.
  • It will take 3 build runs for the leak checking tools to establish themselves. Before the third run expect to see the builds marked as burning. Other than the leak check the builds should compile and test fine.

Using a custom mozconfig

If you want to use setting other than those in the default mozconfigs, you can push an extra file to the $topsrcdir:

• mozconfig-extra with settings to be applied to all mozconfigs
• mozconfig-extra-$platform to apply changes only to that platform's mozconfig, where $platform is one of linux, linux64, win32, macosx, macosx64

The options you enable/disable in your custom mozconfig are appended to the existing config.

The default mozconfigs used for builds are in Hg: http://hg.mozilla.org/build/buildbot-configs/file/6b889c254fee/mozilla2/linux/generic/nightly/mozconfig for example

Disabling specific platforms

You can put exit 1 in any mozconfig-extra-$platform in order to cause it to not compile. This is a temporary workaround but we recommend doing this if there are platforms you know you do not need results for as it will keep our build and test resources going where they are most needed.

BOOKING SCHEDULE

Repo Name	User/Dev Team contact	Booking Dates	Next in Line
projects/alder	jesup, anant: WebRTC integration	2011-09-20 – indefinite	-
projects/birch	bhackett: Maintain copy of m-c without TypeInference	2011-08-22 - 2011-09-27	-
projects/cedar	dietrich: BrowserId add-on integration	2011-08-29 - 2011-12-31	-
projects/holly	Jetpack team: work on supporting running add-ons out of process	2011-08-17 - unknown	-
projects/larch	networking team: Pipelining followed by SSL and SPDY work.	2011-06-13 - 2011-10-1	-
projects/maple	GPHemsley, kscanne: Implementation of BCP 47 (bug 356038)	2011-07-06 – indefinite	-

Be sure to keep a copy of anything you need from the repo prior to unbooking it.