ReleaseEngineering/DisposableProjectRepositories: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(349 intermediate revisions by 93 users not shown)
Line 1: Line 1:
== What is a disposable project branch? ==
== What is a disposable project branch? ==
These are project branches that can be cloned fresh from any mozilla-central based repo with the full gambit of tests enabled.  No l10n or
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 [[Build:TryServerAsBranch]] 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.
nightlies for now. Similar to [[ReleaseEngineering/TryServer|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.
In order to book:


* Sign up below in the [https://wiki.mozilla.org/DisposableProjectBranches#BOOKING_SCHEDULE BOOKING SCHEDULE]
===Do you need a disposable branch?===
* Make a [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=Server%20Operations&short_desc=Requesting%20twig%20repo%20{booked_repo}%20be%20reset&comment=Please%20run%20the%20{script_name}%20and%20reset%20{booked_repo}%20to%20{url} 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'''.
Ask yourself the following:
<pre>
export REPO_PATH= #path to your repo eg: users/lsblakk_mozilla.com/staging
export TWIG= #{maple,cedar,birch} whichever twig you booked


cd /repo/hg/scripts/
'''Does your project have an end date?'''
./reset_pp_repo.sh -s /repo/hg/mozilla/$REPO_PATH -r tip -d $TWIG
 
</pre>
If your answer is '''No''' then you should follow the process at [https://wiki.mozilla.org/ReleaseEngineering:ProjectBranchPlanning Project Branch Planning]
* Sit back and watch your builds and test results roll in ([http://tinderbox.mozilla.org/showbuilds.cgi?tree=Maple Maple], [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Cedar Cedar], [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Birch Birch]).   
 
** '''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.
 
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|BOOKING SCHEDULE]]
* Make a [https://bugzilla.mozilla.org/enter_bug.cgi?product=Developer%20Services&component=Mercurial:%20hg.mozilla.org&short_desc=Requesting%20twig%20repo%20{booked_repo}%20be%20reset&comment=Please%20run%20the%20{script_name}%20and%20reset%20{booked_repo}%20to%20{url} request] (example: {{bug|1518167}}) to VCS to reset the repo for you. You can specify the source repository and target revision to use, or default to mozilla-central:tip. '''Ask that they run the `hgmo-reset-twig.yml` Ansible playbook found in version-control-tools to accomplish this'''.
* '''NOTE''': Your repository will have no hooks enabled after a reset. You'll need to specify in the request if you need any configured.
* After Developer Services runs the reset, they will also notify the teams who operate the automation, so they can adjust their schedulers to recognize the reset. If you don't see the expected builds, check with the automation teams to ensure their reset occurred.
* Sit back and watch your builds and test results roll in (eg [https://treeherder.mozilla.org/#/jobs?repo=birch Birch], [https://treeherder.mozilla.org/#/jobs?repo=cedar Cedar], [https://treeherder.mozilla.org/#/jobs?repo=larch Larch], [https://treeherder.mozilla.org/#/jobs?repo=maple Maple]).   
 
<div id="unbook"></div>
 
===When you're done with one of our fabulous "disposable" project branches===
 
Simply clear your data (bug, contact, dates) from the [[#BOOKING_SCHEDULE|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  ==
== 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:  
The mozconfigs used for builds live in the same source tree as the main code, eg
 
* Firefox: <tt>browser/config/mozconfigs/<platform></tt>
*'''mozconfig-extra''' with settings to be applied to all mozconfigs  
* Mobile Native: <tt>mobile/android/config/mozconfigs/android</tt>
*'''mozconfig-extra-$platform''' to apply changes only to that platform's mozconfig, where $platform is one of linux, linux64, win32, macosx, macosx64
* Mobile XUL: <tt>mobile/xul/config/mozconfigs/android-xul</tt>


The options you enable/disable in your custom mozconfig are '''appended''' to the existing config.  
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).


The default mozconfigs used for builds are available in Hg: [http://hg.mozilla.org/build/buildbot-configs/file/default/mozilla2/ http://hg.mozilla.org/build/buildbot-configs/file/default/mozilla2/]$platform/maple ([http://hg.mozilla.org/build/buildbot-configs/file/default/mozilla2/linux/maple linux example])
==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 [https://bugzilla.mozilla.org/enter_bug.cgi?product=Release%20Engineering here].


===Disabling specific platforms===
Nightly builds and updates are disabled by default but can be enabled on request.
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  ==
== BOOKING SCHEDULE  ==


{| class="data"
{| class="data wikitable"
|-
|-
! Repo Name
! Project Branch
! Regist. bug
! email address of borrower
! User/Dev Team contact  
! User/Dev Team contact  
! Booking Dates   
! Booking Dates   
! Next in Line
! Next in Line
|-
|-
| projects/maple
|
| TabCandy (aza, edilee, mmitcho)
|
| 07/10/10 - 08/31/10
|
|
|
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=ash Ash]
| {{bug|1786042}}
| rob@thunderbird.net
| aleca, darktrojan
| 2022-08-19 - 2023-08-31
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=cypress Cypress]
| {{bug|1899403}}
| mfroman@mozilla.com
| mjf@matrix.mozilla.org
| 2024-01-09 - 2024-12-31
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=elm Elm]
| {{bug|1728404}} libwebrtc update 2H2020
| na-g@nostrum.com
| chew@matrix.mozilla.org
| 2021-07-31 - 2024-12-31
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=cedar Cedar]
| {{bug|1820001}} iOS prototyping
| jeevans@mozilla.com, csadilek@mozilla.com
| csadilek
| 2023-03-02 - 2024-03-31
|
|-
| <strike>[https://treeherder.mozilla.org/#/jobs?repo=fig Fig]</strike>
| retired
| retired
| retired
| retired
| retired
|-
| <strike>[https://treeherder.mozilla.org/#/jobs?repo=gum Gum]</strike>
| retired
| retired
| retired
| retired
| retired
|-
| [https://treeherder.mozilla.org/#/jobs?repo=holly Holly]
| {{bug|1599905}}
| jewilde@mozilla.com, tom@mozilla.com
| <-
| 2019-12-02 - 2020-04-02
| -
| -
|-
|-
| projects/cedar
| [https://treeherder.mozilla.org/#/jobs?repo=larch Larch]
| -
| {{bug|1874491}} desktop sidebar
| elee@mozilla.com
| Mardak, tarek
| 2024-01-16 - 2025-01-16
|
|-
| [https://treeherder.mozilla.org/#/jobs?repo=oak Oak]
| {{bug|1819778}} Android Monorepo project: Prototyping move to M-C.
| jlorenzo@mozilla.com, gluong@mozilla.com
| jlorenzo, gl
| 2023-03-02 - 2024-06-30
| -
| -
|}
Be sure to keep a copy of anything you need from the repo prior to [[#unbook|unbooking]] it.
== Indefinite booking  ==
See also [[ReleaseEngineering/SpecialBranches]] for more info on these branches.
{| class="data wikitable"
|-
! Project Branch
! Regist. bug
! email address of borrower
! User/Dev Team contact
! Booking Dates
|-
| [https://treeherder.mozilla.org/#/jobs?repo=date Date]
| disabled
| disabled
| disabled
| DO NOT USE - https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectRepositories
|-
| [https://treeherder.mozilla.org/#/jobs?repo=jamun Jamun]
| {{bug|1666242}}
| rob@thunderbird.net
| comm-central as a branch
| 2020-10-21 - ?
|-
| [https://treeherder.mozilla.org/#/jobs?repo=birch Birch]
| {{bug|1426132}}
| -
| -
| Unused
| 2023-07-20 - indefinite
|-
| [https://treeherder.mozilla.org/#/jobs?repo=maple Maple]
| {{bug|1397773}}
| hneiva@mozilla.com releng@mozilla.com
| MacOS Signing Changes
| 2023-07-28 - indefinite
|-
|-
| projects/birch
| [https://treeherder.mozilla.org/#/jobs?repo=pine Pine]
| hw accelerated gfx (joe)
| {{bug|1845368}}
| 2010-08-12 - 2010-09-30
| bytesized@mozilla.com
| Desktop Integrations Team
| 2023-07-27 - indefinite
| -
| -
|}
|}

Latest revision as of 20:41, 28 May 2024

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 1518167) to VCS to reset the repo for you. You can specify the source repository and target revision to use, or default to mozilla-central:tip. Ask that they run the `hgmo-reset-twig.yml` Ansible playbook found in version-control-tools to accomplish this.
  • NOTE: Your repository will have no hooks enabled after a reset. You'll need to specify in the request if you need any configured.
  • After Developer Services runs the reset, they will also notify the teams who operate the automation, so they can adjust their schedulers to recognize the reset. If you don't see the expected builds, check with the automation teams to ensure their reset occurred.
  • Sit back and watch your builds and test results roll in (eg Birch, Cedar, Larch, Maple).

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.

BOOKING SCHEDULE

Project Branch Regist. bug email address of borrower User/Dev Team contact Booking Dates Next in Line
Ash bug 1786042 rob@thunderbird.net aleca, darktrojan 2022-08-19 - 2023-08-31
Cypress bug 1899403 mfroman@mozilla.com mjf@matrix.mozilla.org 2024-01-09 - 2024-12-31
Elm bug 1728404 libwebrtc update 2H2020 na-g@nostrum.com chew@matrix.mozilla.org 2021-07-31 - 2024-12-31
Cedar bug 1820001 iOS prototyping jeevans@mozilla.com, csadilek@mozilla.com csadilek 2023-03-02 - 2024-03-31
Fig retired retired retired retired retired
Gum retired retired retired retired retired
Holly bug 1599905 jewilde@mozilla.com, tom@mozilla.com <- 2019-12-02 - 2020-04-02 -
Larch bug 1874491 desktop sidebar elee@mozilla.com Mardak, tarek 2024-01-16 - 2025-01-16
Oak bug 1819778 Android Monorepo project: Prototyping move to M-C. jlorenzo@mozilla.com, gluong@mozilla.com jlorenzo, gl 2023-03-02 - 2024-06-30 -

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

Indefinite booking

See also ReleaseEngineering/SpecialBranches for more info on these branches.

Project Branch Regist. bug email address of borrower User/Dev Team contact Booking Dates
Date disabled disabled disabled DO NOT USE - https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectRepositories
Jamun bug 1666242 rob@thunderbird.net comm-central as a branch 2020-10-21 - ?
Birch bug 1426132 - Unused 2023-07-20 - indefinite
Maple bug 1397773 hneiva@mozilla.com releng@mozilla.com MacOS Signing Changes 2023-07-28 - indefinite
Pine bug 1845368 bytesized@mozilla.com Desktop Integrations Team 2023-07-27 - indefinite -
Retrieved from "https://wiki.allizom.org/index.php?title=ReleaseEngineering/DisposableProjectRepositories&oldid=1250901"