663128 - New project branch request - fx-team

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P3)

Description

[Johnathan Nightingale [:johnath]]

I'd like a long-lived (no end date) integration branch for the Firefox team to use instead of landing directly on mozilla-central.

Answers to the questions from https://wiki.mozilla.org/ReleaseEngineering:ProjectBranchPlanning below:

Project name: fx-team

For builds:
All platforms or subset of platforms currently building mozilla-central?
 - All platforms on m-c

Will you use the mozilla-central mozconfigs or will you need custom ones?
 - moz-central should be fine

Nightly builds?
 - yes please

Need unittests?
All platforms or subset of platforms currently testing mozilla-central? 
 - All tests on m-c

Mobile Builds?
All platforms or subset of platforms currently building mobile-browser? 
 - don't think we need mobile coverage here

Need Talos?
All talos suites or a subset of suites run on mozilla-central? 
 - all talos suites

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 
- TBD, but for now let's make it me

Timeline:
When should this branch go live?
 - this isn't critical, but would be nice to have as soon as convenient

Approx expected life span of project branch? 
 - long-lived, no anticipated end date

Comment 1

[Johnathan Nightingale [:johnath]]

(In reply to comment #0)
> 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 
> - TBD, but for now let's make it me

Actually - Gavin just volunteered!

Comment 2

[Lukas Blakk [:lsblakk] use ?needinfo]

I'm have to block this on bug 661525 because at this moment, adding new branches is killing our test masters and so we're trying to mitigate that by splitting out the masters by platform. Should only take a day or two to get this sorted according to catlee so if this bug doesn't get any love early next week please feel free to verbally abuse me in IRC until I get on it.

Comment 3

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: fx-team configs

Comment 4

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: data.sql patch for fx-team branch

Comment 5

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: fx-team added to tbpl

Comment 6

[Lukas Blakk [:lsblakk] use ?needinfo]

Status:

* Filed ServerOps bug to create repo
* Filed ServerOps bug to insert branch into graphserver-{staging,production}
* Created tinderbox page for the branch to report to http://tinderbox.mozilla.org/showbuilds.cgi?tree=Fx-Team
* Patch attached to add the branch to tbpl 
* Patch attached to add branch to buildbot-configs/mozilla/project_branches
* Patch attached for updating graphs sql

Now we wait for repo/graphserver/test-master load balancing.

Comment 7

[Jesse Ruderman]

<bikeshed>Using the word "team" sounds exclusionary. How about "fx-frontend"?</bikeshed>

Comment 8

[:Gavin Sharp [email: [e-mail]]]

fx-team matches the channel name, and the repo/patches have already been created as "fx-team", I don't think we need to change them. Everyone's allowed to be part of fx-team!

Comment 9

[Lukas Blakk [:lsblakk] use ?needinfo]

Comment on attachment 538449 [details] [diff] [review]
fx-team configs

landed configs on default http://hg.mozilla.org/build/buildbot-configs/rev/ab2d5470c8e6

Comment 10

[Lukas Blakk [:lsblakk] use ?needinfo]

Comment on attachment 538450 [details] [diff] [review]
data.sql patch for fx-team branch

landed http://hg.mozilla.org/graphs/rev/e3cd44360978

Comment 11

[Lukas Blakk [:lsblakk] use ?needinfo]

Comment on attachment 538451 [details] [diff] [review]
fx-team added to tbpl

landed and deployed on tinderboxpushlog http://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/rev/d2c3040d58c3

Comment 12

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: turn off mobile builds for fx-team

This is new since the patches were created, adding ['firefox'] to enabled_products since this branch does not want mobile builds.

Comment 13

[Rail Aliiev [:rail]]

Comment on attachment 541651 [details] [diff] [review]
turn off mobile builds for fx-team

Looks good!

Comment 14

[Lukas Blakk [:lsblakk] use ?needinfo]

Comment on attachment 541651 [details] [diff] [review]
turn off mobile builds for fx-team

and now the mobile builds are off as requested (on default, will get into production at the same time as the general configs) http://hg.mozilla.org/build/buildbot-configs/rev/c56b71d48623

Comment 15

[Lukas Blakk [:lsblakk] use ?needinfo]

I'm about to go away for a week so I've landed this branch's configs and it will get scooped up in the next reconfig of our automation masters.  Here is a checklist of what is in place:

* Repo has been created
* Tinderbox page exists at http://tinderbox.mozilla.org/showbuilds.cgi?tree=Fx-Team
* TBPL exists at http://tbpl.mozilla.org/?tree=Fx-Team
* Graphserver entries (production, staging) have been done
* Configs have been landed to run per-checkin builds (firefox only, no mobile), with nightly builds enabled, using mozilla-central mozconfigs, with the same unittests as mozilla-central

The first round of builds on this branch once it is live will burn due to missing previous leak logs but a second run should clear that up.

Comment 16

[Lukas Blakk [:lsblakk] use ?needinfo]

I should point out that RelEng will reserve the right to back out this branch should it cause too much load on the test masters.  Since at least some of the master load is now on split-by-platform masters I hope that won't be necessary.  Catlee gets to make that call if there are any issues next week.

Comment 17

[Lukas Blakk [:lsblakk] use ?needinfo]

Looks like this is being used now with successful outcomes.  Resolving.