- 1 What is a disposable project branch?
- 2 Using a custom mozconfig
- 3 Enabling/Disabling of platforms, tests, nightly updates
- 4 BOOKING SCHEDULE
- 5 Indefinite booking
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
NOTE: The number of disposable branches is limited by CI capacity. If there are no available branches, contact the owners of existing branches to see if you can "sub let".
- Sign up below in the BOOKING SCHEDULE
- Make a request (example: bug 951811) 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 or comm-central 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
- NOTE: Coordinate with IT when this repo gets reset to push immediately without hitting the webheads. Otherwise, the permissions won't be set correctly.
- NOTE: Your repository will have no hooks enabled after a reset. You'll need to specify in the request if you need any configured.
- Sit back and watch your builds and test results roll in (eg Alder, Birch, Cedar,Holly, Larch, Maple).
- Special note: the first push to your newly cloned repo may not trigger builds if the repo had been pushed to previously, which is bug 774862. If it does not, please re-open the bug and move it to Release Engineering :: General Automation with a comment 'Please reconfigure the build scheduler'.
When you're done with one of our fabulous "disposable" project branches
Simply clear your data (bug, contact, dates) from the BOOKING SCHEDULE below. If someone is listed in the "Next in Line" column, please let them know you are done.
That's all there is to it!
Using a custom mozconfig
The mozconfigs used for builds live in the same source tree as the main code, eg
- Firefox: browser/config/mozconfigs/<platform>
- Mobile Native: mobile/android/config/mozconfigs/android
- Mobile XUL: mobile/xul/config/mozconfigs/android-xul
The 'nightly' file is used for optimised builds, 'debug' for debug. If you are unsure which file you need consult a build log to see which is used. You can adjust these as needed on your branch, and they will be carried over to mozilla-central when you merge back. Please take care with any mozconfig changes you merge back (eg exclude local conveniences).
Enabling/Disabling of platforms, tests, nightly updates
If the specific builds/tests you want are not enabled, or if there are builds/tests which you do not need on your branch, ask RelEng to enable/disable them by filing a bug here.
Nightly builds and updates are disabled by default but can be enabled on request.
|Project Branch||Regist. bug||email address of borrower||User/Dev Team contact||Booking Dates||Next in Line|
|Alder||bug email@example.com||Buildbot <-> Taskcluster Bridge testing||2015-04-20 - 2015-06-30|
|Ashfirstname.lastname@example.org||2015-02-09 - TBD|
|Cypressemail@example.com||2014-12-15 - 2015-03-01|
|Date||bug firstname.lastname@example.org||Release automation changes||2015-01-11 - 2015-03-31|
|Elm||bug email@example.com||Gtk+3 work||2014-06-19 - ??? PENDING||-|
|Figfirstname.lastname@example.org||Loop staging||2014-09-23 - email@example.com|
|Gumfirstname.lastname@example.org||Profile testing||2015-01-20 - 2015-03-31|
|Holly||bug email@example.com||:billm on IRC, e10s||2013-03-15 - 2014-11-01|
|Jamun||bug firstname.lastname@example.org, email@example.com||Nested OOP||2015-03-25 - 2015-12-31|
|Larchfirstname.lastname@example.org||Project Graphene||Until 2015-04-30|
|Maple||bug email@example.com||Releng||2015-03-11 - ???||-|
|Oak||bug 790467 and other risky updater firstname.lastname@example.org, email@example.com||spohl, rstrong||2012-09-11 - 2015-12-31 PENDING||-|
|Pine||bug firstname.lastname@example.org||:gwagner, debug B2G builds and unit tests||2013-10-21 - indefinite PENDING||-|
Be sure to keep a copy of anything you need from the repo prior to unbooking it.
See also ReleaseEngineering/SpecialBranches for more info on these branches.
|Project Branch||Regist. bug||email address of borrower||User/Dev Team contact||Booking Dates|
|Birch||bug email@example.com||disabled||2014-05-15 - indefinite PENDING|
|Cedarfirstname.lastname@example.org||new build/test testing for #ateam and #releng||2012-06-25 - indefinite PENDING|