Closed Bug 667734 Opened 13 years ago Closed 13 years ago

Customize disposable branch [maple] for bcp47 project booking

Categories

(Release Engineering :: General, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: GPHemsley, Assigned: lsblakk)

References

(Blocks 1 open bug)

Details

(Whiteboard: [project branch] [bcp47])

Attachments

(2 files)

Project name:
    http://hg.mozilla.org/projects/bcp47

For builds:
    All platforms currently building mozilla-central.
    Default mozilla-central mozconfig.
    Nightly builds with updates.

Need unittests?
    All platforms currently testing mozilla-central.

Mobile Builds?
    All platforms currently building mobile-browser.

Need Talos?
    No Talos at this time. 

Name of the contact person for this branch who will:
    Be doing periodic refreshes from parent
    Be contact person for misc setup questions
    Decide when to land back project branch onto parent
    Decide when to terminate the project branch 
        Gordon P. Hemsley <gphemsley@gmail.com>

Timeline:
    When should this branch go live? ASAP.
    Approx expected life span of project branch? Until bug 356038 is RESOLVED FIXED.
Blocks: 667735
Blocks: 667822
I'm going to assume that this is blocked by bug 661525 like the other currently-open project branch bugs.
Depends on: 661525
Actually since this project branch feasibly has an end date (when bug 356038 is fixed) it doesn't fit with the named project branch criteria. You could book one of the three currently available 'disposable' branches for this work here: https://wiki.mozilla.org/DisposableProjectBranches and we can be sure to tweak anything that doesn't already meet your request specifics.  It would have talos enabled and that can be disabled to save cycles, and other than that the wiring should be pretty much good to go as soon as you get a clean clone to that branch.
(In reply to comment #2)
> Actually since this project branch feasibly has an end date (when bug 356038
> is fixed) it doesn't fit with the named project branch criteria. You could
> book one of the three currently available 'disposable' branches for this
> work here: https://wiki.mozilla.org/DisposableProjectBranches and we can be
> sure to tweak anything that doesn't already meet your request specifics.  It
> would have talos enabled and that can be disabled to save cycles, and other
> than that the wiring should be pretty much good to go as soon as you get a
> clean clone to that branch.

Well, the reason I didn't go that route originally was because that word "feasibly". There are a lot of facets to this project, and that bug is just a tracking bug. There are currently 16 bugs that are related, and we are anticipating that work could take up to a year to complete, if not longer.

It was my impression that the disposable branches were for quick things that only take a couple of months. I didn't want to tie up a disposable branch with such a long project.

If you don't see that as a problem, though, then sure, we can go that route. How shall I modify this proposal?
There's no time limit on booking those branches and we have empty ones, so definitely go ahead and take one. The instructions for filing the IT bug required are in that wiki doc. Report back to this bug with which branch you're taking and I can put up the temporary customization disabling Talos for that branch.
Summary: New project branch request: bcp47 → Customize disposable branch [branch-name] for bcp47 project booking
Depends on: 669598
Alright, I reserved the maple branch in bug 669598.
Summary: Customize disposable branch [branch-name] for bcp47 project booking → Customize disposable branch [maple] for bcp47 project booking
(In reply to comment #5)
> Alright, I reserved the maple branch in bug 669598.

Great.  One more thing - updates. If we enable nightly builds with updates and your branch is using the mozilla-central mozconfigs your nightly builds will update to that branch. If on the other hand you want nightly updates to stay on your current branch we'll need to use the generic mozconfigs that the project branches use with a custom mozconfig-extra pointing to a different nightly update channel and also that nightly channel will need to be activated.  Which do you prefer?
(In reply to comment #6)
> (In reply to comment #5)
> > Alright, I reserved the maple branch in bug 669598.
> 
> Great.  One more thing - updates. If we enable nightly builds with updates
> and your branch is using the mozilla-central mozconfigs your nightly builds
> will update to that branch. If on the other hand you want nightly updates to
> stay on your current branch we'll need to use the generic mozconfigs that
> the project branches use with a custom mozconfig-extra pointing to a
> different nightly update channel and also that nightly channel will need to
> be activated.  Which do you prefer?

Oh, yeah, it probably wouldn't help us to update users to the mozilla-central channel. So I suppose we'll need modifications for our own channel. (Would that be 'maple' or 'bcp47'? Or do I make that decision later?)
For re-usability in future bookings of this branch it would be the nightly-maple channel. I'll get that working.
this will use the generic mozconfigs and in the maple repo you can check in mozconfig-extra with:

ac_add_options --enable-update-channel=nightly-maple

in order to set the update channel properly for this branch which should override the setting for nightly update channel across all platforms (example http://hg.mozilla.org/build/buildbot-configs/file/6b889c254fee/mozilla2/linux/generic/nightly/mozconfig)

see: https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectBranches#Using_a_custom_mozconfig
Attachment #544220 - Flags: review?(nrthomas)
No longer depends on: 661525
Attachment #544220 - Flags: review?(nrthomas) → review+
Attachment #544221 - Flags: review?(nrthomas) → review+
Comment on attachment 544221 [details] [diff] [review]
enable maple nightly updates in aus

Checking in config-dist.php;
/cvsroot/mozilla/webtools/aus/xml/inc/config-dist.php,v  <--  config-dist.php
new revision: 1.152; previous revision: 1.151
done

$ cvs tag AUS2_PRODUCTION config-dist.php 
W config-dist.php : AUS2_PRODUCTION already exists on version 1.151 : NOT MOVING tag to version 1.152

$ cvs tag -F AUS2_PRODUCTION config-dist.php 
T config-dist.php
Attachment #544221 - Flags: checked-in+
Comment on attachment 544220 [details] [diff] [review]
customizations for maple branch configs

http://hg.mozilla.org/build/buildbot-configs/rev/37b3f23d4778

landed on default
Attachment #544220 - Flags: checked-in+
Depends on: 669951
I kicked off my first builds earlier today!

Builds are starting to come in green... but is it just me, or is Talos still running on them?
http://tinderbox.mozilla.org/showbuilds.cgi?tree=Maple

Also, while I'm here, what else needs to be done to resolve this as FIXED?
I believe that a reconfig of our buildbot masters will get rid of those pesky Talos runs, so I will come back and close this once that is confirmed.
So the talos tests are now turned off, I'm resolving this. If your updates don't work please reopen so I can investigate but otherwise this branch should be configured as requested.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
(In reply to comment #15)
> So the talos tests are now turned off, I'm resolving this. If your updates
> don't work please reopen so I can investigate but otherwise this branch
> should be configured as requested.

Yeah, it doesn't look like updates are working. The nightlies are being generated just fine, but checking for updates tells me that I'm up-to-date on a week-old build.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Lukas, we were missing the symlinks that map requests for mac builds to maple/Darwin_x86_64-gcc3. Fixed, as ffxbld
 rsync -av ~/template/ /opt/aus2/incoming/2/Firefox/maple/
as documented in https://wiki.mozilla.org/ReleaseEngineering:ProjectBranchPlanning#Release_Engineering_Project_Branch_Creation_Checklist.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: