659638 - new integration (project) branch: mozilla-inbound

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[Mike Connor [:mconnor]]

> *Project name:*
> Your project name will also be used for the repo name (eg: hg.mozilla.org/projects/jaegermonkey) - please state if you have an existing repo you're looking to use instead of a projects/ one.
> Note: project names should avoid using confusing/overloaded terms, like "build", "firefox", "release"... 

We'll create mozilla-inbound in the same location as mozilla-central

> *For builds:*
> All platforms or subset of platforms currently building mozilla-central (including mobile platforms)?

All platforms.

> Will you use the mozilla-central mozconfigs or will you need custom ones?

mozilla-central.

> Nightly builds? 

Yes.

> Need unittests?

Yes.

> All platforms or subset of platforms currently testing mozilla-central? 

All platforms.

> Need Talos?

Yes

> All talos suites or a subset of suites run on mozilla-central? 

All talos suites

> Contacts:
> Name of the key contacts 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 

rnewman
philikon
ehsan

> *Timeline:*
> When should this branch go live?

ASAP.

> Approx expected life span of project branch? 

∞

Comment 1

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: mozilla-inbound configs

Comment 2

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: add mozilla-inbound to data.sql

Comment 3

[Armen [:armenzg]]

Comment on attachment 536599 [details] [diff] [review]
add mozilla-inbound to data.sql

*stamp*

Comment 4

[Lukas Blakk [:lsblakk] use ?needinfo]

Joduinn and mconnor have discussed the location of this repo (whether it can live in the top level) and agreed upon creating an integration dir under hg.m.o for infinite-life projects that will be merged into mozilla-central as needed so that they are distinct in path name from projects/ but not in the top level.

Comment 5

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: mozilla-inbound configs

Comment 6

[Lukas Blakk [:lsblakk] use ?needinfo]

Comment on attachment 536599 [details] [diff] [review]
add mozilla-inbound to data.sql

http://hg.mozilla.org/graphs/rev/3d1e1a7132aa

Comment 7

[Lukas Blakk [:lsblakk] use ?needinfo]

Comment on attachment 537566 [details] [diff] [review]
mozilla-inbound configs

http://hg.mozilla.org/graphs/rev/3d1e1a7132aa on default, ready for reconfig on Tuesday

Comment 8

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: mozilla-inbound tbpl

Comment 9

[Lukas Blakk [:lsblakk] use ?needinfo]

Comment on attachment 537628 [details] [diff] [review]
mozilla-inbound tbpl

http://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/rev/67b1f21896bb
landed, and deployed on tbpl.m.o

Comment 10

[Lukas Blakk [:lsblakk] use ?needinfo]

philikon is going to push a dummy cset so we can verify this is complete.

Comment 11

[Philipp von Weitershausen [:philikon]]

Pushed: http://tbpl.mozilla.org/?tree=Mozilla-Inbound&rev=a58cdcdcac5f

Comment 12

[(no longer active)]

We should also make sure to enable the regression detection scripts for mozilla-inbound before beginning to use it.  The current situation with perf regression detection on cedar is sad (basically, the scripts only watch m-c, so we sometimes get notified of regressions on an entire merge...)

Comment 13

[Chris AtLee [:catlee]]

(In reply to comment #12)
> We should also make sure to enable the regression detection scripts for
> mozilla-inbound before beginning to use it.  The current situation with perf
> regression detection on cedar is sad (basically, the scripts only watch m-c,
> so we sometimes get notified of regressions on an entire merge...)

I just enabled this for mozilla-inbound. It could be a bit noisy at first until enough data is accumulated.

Comment 14

[Philipp von Weitershausen [:philikon]]

Thanks, Chris! Seems like everything's working fine, so I'm resolving this bug. Thanks everybody who made this happen!