Closed Bug 1049930 Opened 10 years ago Closed 10 years ago

Create builds for Dolphin on mozilla-central, mozilla-inbound, b2g-inbound, fx-team, and mozilla-aurora

Categories

(Release Engineering :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jsmith, Assigned: nthomas)

References

Details

Attachments

(3 files, 3 obsolete files)

Dolphin is our target reference device for SPRD, so we need to ensure that we can test Dolphin on all branches under active development. This is especially important for allowing us to test Moz RIL, since Moz RIL is only supported officially on SPRD devices right now.

Current branch needs:

* m-c
* b2g32
* aurora
* b2g-inbound
* mozilla-inbound
Nick - Can you find someone to look into this? This will help unblock testing of Moz RIL on SPRD devices for other branches under development.
Flags: needinfo?(nthomas)
We are currently building dolphin for 
* mozilla-b2g30_v1_4 only
* dep builds periodically, at 00:30, 6:30 and 12:30   (go into tinderbox-builds/)
* nightly builds twice a day, 00:02 and 16:02   (go into nightly/)
* eng and non-eng for both of those

So we should stop those and add the new branches, by the sounds of comment #0. Questions
* Are periodic builds still fine ? The alternative is on every landing
* We currently only do nightlies on m-c, aurora, and m-b2g32, you'd have tinderbox-builds for the rest. OK ?

Also, aurora has no device builds this cycle, but they'll be back for the next one and we can get the configuration done now.
Flags: needinfo?(nthomas)
(In reply to Nick Thomas [:nthomas] from comment #2)
> We are currently building dolphin for 
> * mozilla-b2g30_v1_4 only
> * dep builds periodically, at 00:30, 6:30 and 12:30   (go into
> tinderbox-builds/)
> * nightly builds twice a day, 00:02 and 16:02   (go into nightly/)
> * eng and non-eng for both of those
> 
> So we should stop those and add the new branches, by the sounds of comment

Actually, we still need 1.4 builds right now, so we shouldn't stop generating builds there.

> #0. Questions
> * Are periodic builds still fine ? The alternative is on every landing

Periodic builds are fine to use.

> * We currently only do nightlies on m-c, aurora, and m-b2g32, you'd have
> tinderbox-builds for the rest. OK ?

Yes.

> 
> Also, aurora has no device builds this cycle, but they'll be back for the
> next one and we can get the configuration done now.

Right.
Adds these builders:
b2g_b2g-inbound_dolphin_periodic
b2g_b2g-inbound_dolphin_eng_periodic
--
b2g_mozilla-inbound_dolphin_periodic
b2g_mozilla-inbound_dolphin_eng_periodic
--
b2g_mozilla-central_dolphin_periodic
b2g_mozilla-central_dolphin_nightly
b2g_mozilla-central_dolphin_eng_periodic
b2g_mozilla-central_dolphin_eng_nightly
--
b2g_mozilla-b2g32_v2_0_dolphin_periodic
b2g_mozilla-b2g32_v2_0_dolphin_nightly
b2g_mozilla-b2g32_v2_0_dolphin_eng_periodic
b2g_mozilla-b2g32_v2_0_dolphin_eng_nightly

And should be the same on aurora as on mozilla-inbound.
Assignee: nobody → nthomas
Status: NEW → ASSIGNED
Attachment #8471315 - Flags: review?(rail)
Attachment #8471315 - Flags: review?(rail) → review+
Comment on attachment 8471315 [details] [diff] [review]
[buildbot-configs] Turn on more dolphin builds

https://hg.mozilla.org/build/buildbot-configs/rev/8832f208bfe9

Will go live in the next buildbot reconfig.
Attachment #8471315 - Flags: checked-in+
Which happened earlier today but the builds are burning; philor is going to hide them. Need to add b2g/config/dolphin/config.json to all the repos it's not in already.
Aurora's not an active B2G branch during this cycle. Why are we trying to schedule these builds there?

Also, does Bumper Bot need any changes or will things just work?
(In reply to Jason Smith [:jsmith] from comment #0)
> Dolphin is our target reference device for SPRD, so we need to ensure that
> we can test Dolphin on all branches under active development. This is
> especially important for allowing us to test Moz RIL, since Moz RIL is only
> supported officially on SPRD devices right now.

FWIW, numerous 1.4 blockers (primarily in RIL code no less) have been denied 2.0 uplift due to lack of applicability to that release. Not sure what this bug means for that.
    1.68  for branch in BRANCHES:
    1.69 -    if branch not in ('mozilla-b2g30_v1_4',):
    1.70 +    if branch not in ('mozilla-b2g30_v1_4', 'mozilla-b2g32_v2_0',
    1.71 +                      'mozilla-aurora', 'mozilla-central', 'mozilla-inbound',
    1.72 +                      'b2g-inbound'):

Per the Job Visibility Policy, fx-team also needs to run these.
https://wiki.mozilla.org/Sheriffing/Job_Visibility_Policy#3.29_Runs_on_mozilla-central_and_all_trees_that_merge_into_it
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #7)
> Aurora's not an active B2G branch during this cycle. Why are we trying to
> schedule these builds there?

We're not actually. b2g builds are globally disabled on aurora by
 http://hg.mozilla.org/build/buildbot-configs/file/ad66388f3636/mozilla/b2g_config.py#l1230
They are added in the code block in comment #9 so that we get aurora builds when that is undone.

> Also, does Bumper Bot need any changes or will things just work?

Maybe, I will check.
Attached patch [buildbot-configs] Add fx-team (obsolete) — Splinter Review
Attachment #8472799 - Flags: review?(rail)
Not sure what if any changes dolphin.xml is going to need on the non-1.4 branches of b2g-manifest as well.
Attachment #8472799 - Flags: review?(rail) → review+
Nick - After further discussion with rel man, they desire that we don't have Dolphin builds for 2.0, since we didn't uplift a bunch of patches to ensure Moz RIL works well on Dolphin on 2.0. That means we don't need the 2.0 builds. Can you remove them?

Sorry for the last minute change though.
Flags: needinfo?(nthomas)
Comment on attachment 8471315 [details] [diff] [review]
[buildbot-configs] Turn on more dolphin builds

I backed this out while I sort out bumper config and in-tree files.
Attachment #8471315 - Flags: checked-in+ → checked-in-
Flags: needinfo?(nthomas)
This combines the two earlier patches, and drops the mozilla-b2g32_v2_0 references. Carrying review over. Will land last, once everything else is in.
Attachment #8471315 - Attachment is obsolete: true
Attachment #8472799 - Attachment is obsolete: true
Attachment #8473257 - Flags: review+
Depends on: 1054061
This is written from inspection of the existing configs, and not well untested. The intention is to bump b2g/config/dolphin/sources.xml on b2g-inbound. I'll check it closer once we get repos synced.
Attached patch [b2g-inbound] WIP of config.json (obsolete) — Splinter Review
* not sure if we need gecko+gaia updates or not
* missing sources.xml (depends on bumper setup)
Summary: Create daily builds for Dolphin on all branches under active development → Create builds for Dolphin on mozilla-central, mozilla-inbound, b2g-inbound, fx-team, and mozilla-aurora
Comment on attachment 8473339 [details] [diff] [review]
[mozharness] Bump dolphin manifests, include spreadtrum mapping

This is copied over from the 1.4 config where we already had Dolphin builds.
Attachment #8473339 - Flags: review?(catlee)
* config.json is from copying the 1.4 file and updating the l10n paths, dropping b2g_manifest_branch
* sources.xml from running b2g_bumper locally
Attachment #8473352 - Attachment is obsolete: true
Attachment #8475075 - Flags: review?(catlee)
Attachment #8473339 - Flags: review?(catlee) → review+
Attachment #8475075 - Flags: review?(catlee) → review+
Comment on attachment 8475075 [details] [diff] [review]
[b2g-inbound] in tree config and source manifest

https://hg.mozilla.org/integration/b2g-inbound/rev/b7d53b3626be
Attachment #8475075 - Flags: checked-in+
Keywords: leave-open
Comment on attachment 8473339 [details] [diff] [review]
[mozharness] Bump dolphin manifests, include spreadtrum mapping

https://hg.mozilla.org/build/mozharness/rev/5f0136207f66 on default
Attachment #8473339 - Flags: checked-in+
Comment on attachment 8473339 [details] [diff] [review]
[mozharness] Bump dolphin manifests, include spreadtrum mapping

Attachment 8473339 [details] [diff] now merged into production branch too:
https://hg.mozilla.org/build/mozharness/rev/7771c9623c92
Comment on attachment 8473257 [details] [diff] [review]
[buildbot-configs] Combined patch, less mozilla-b2g32_v2_0

in-tree files are merged around, and both builds work fine in staging (except for expected failures to upload to prod host).

https://hg.mozilla.org/build/buildbot-configs/rev/be307b08bbda
Attachment #8473257 - Flags: checked-in+
in production :)
Green. Unhidden on TBPL. All done.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Removing leave-open keyword from resolved bugs, per :sylvestre.
Keywords: leave-open
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: