875989 - [Tracking bug] create new branch "integration/b2g-inbound"

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

tl;dr: we've used birch as experimental b2g-inbound for the last 6 weeks. It works great. Sheriffs and devs love it, so we're making it permanent.


Before the Madrid workweek 15apr2013, we started an experiment of using "birch" as a branch to reduce load on mozilla-inbound. All b2g developer landing gecko changes would use "birch", and sheriffs would monitor/backout/land-to-central as needed. All non-b2g developers landing gecko changes continue to use mozilla-inbound or mozilla-central as usual.  

This helps reduce the volume of checkins on mozilla-inbound, which helps reduce the likelihood of m-i treeclosure. If m-i is closed, b2g changes to gecko can continue to land on birch/b2g-inbound. If birch/b2g-inbound is closed, non-b2g changes to gecko can continue to land on m-i. This reduces the pressures on sheriffs during treeclosure of either branch. In further goodness, even without any tree closures, using two inbounds like this has increased the total number of checkins that can land. 

We've used this process now for ~6 weeks and its been wildly successful, with sheriffs+developers, so we're going to make this permanent. "integration/b2g-inbound" should be created beside "integration/mozilla-inbound".

In addition to creating repos, this will require changes to hg-git replications, buildbot configs, tbpl, graphserver... which should be filed as separate dep bugs.

Once all this is done, and tested, we can coordinate with sheriffs to transition developer-usage over to b2g-inbound, and afterwards can file bug to free up birch for normal short-term-rental use.

Comment 1

[Ryan VanderMeulen [:RyanVM]]

Can I bikeshed on the name here? I would prefer inbound-b2g instead so that we can have a sort-of inbound-xxx convention as we possibly add more down the road (for example, maybe inbound-alt as the official name for our current cypress/inbound2 experiment).

Comment 2

[Ed Morley [:emorley]]

Agree with Ryan, inbound-b2g would be preferable.

Unrelated, we'll also need to make sure we enable the commit message hook, since it's not currently enabled for Birch (see bug 887184 comment 0).

Comment 3

[Hal Wine [:hwine] use NI!]

Per email discussion, we'll use the following pattern for all inbound branches:
  integration/${project}-inbound

This is consistant with the current m-i:
  integration/mozilla-inbound
so this repository will be
  integration/b2g-inbound