Flame 2.5 needs FOTA builds

RESOLVED FIXED

Status

Taskcluster
General
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: nhirata, Assigned: wcosta)

Tracking

Details

Attachments

(1 attachment)

1) due to the size limitation issue, we had decided to FOTA for 2.5
2) There's a gecko/gaia specific FOTA that we need to do.

See https://bugzilla.mozilla.org/show_bug.cgi?id=1037056
Flags: needinfo?(wcosta)
Note, looks like the pvtbuild/buildbot makes FOTA 2.5 builds.  TC builds look like OTA.

So we either need to turn pvtbuilds /build bot back on for 2.5 or have TC builds create FOTA instead.
see bug 1223259 : https://treeherder.allizom.org/#/jobs?repo=mozilla-b2g44_v2_5&revision=361f2673aadc
See Also: → bug 1223259
(Assignee)

Updated

2 years ago
Assignee: nobody → wcosta
Status: NEW → ASSIGNED
Flags: needinfo?(wcosta)
(Assignee)

Comment 3

2 years ago
Created attachment 8685696 [details] [diff] [review]
Enable fota builds for flame and nexus devices. r=jlund
(Assignee)

Comment 4

2 years ago
Comment on attachment 8685696 [details] [diff] [review]
Enable fota builds for flame and nexus devices. r=jlund

Try:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=2ec5b938041a

Builds:
https://tools.taskcluster.net/task-inspector/#Fa4P-yinQiiPvQCz2DVzig/
https://tools.taskcluster.net/task-inspector/#KYszyvBeR8K4SYrQZzAzYw/

This needs to uplift to b2g44_v2_5, but the channel name needs updating to nightly-b2g44.
Attachment #8685696 - Flags: review?(jlund)

Comment 5

2 years ago
Comment on attachment 8685696 [details] [diff] [review]
Enable fota builds for flame and nexus devices. r=jlund

Review of attachment 8685696 [details] [diff] [review]:
-----------------------------------------------------------------

lgmt

::: testing/mozharness/configs/b2g/taskcluster-phone-fota.py
@@ +37,5 @@
> +    "env": {
> +        "GAIA_OPTIMIZE": "1",
> +        "WGET_OPTS": "-c -q"
> +    },
> +    "update_types": [ "ota", "fota" ],

is this the only difference between taskcluster-phone-ota.py and this file? If so, we should look into passing update_types via cmd line and sharing the config. Shame to have all this duplication.

::: testing/taskcluster/tasks/builds/b2g_nexus_5l_ota_debug.yml
@@ +23,5 @@
>        B2G_DEBUG: 0
>        TARGET: 'nexus-5-l'
>        DEBUG: 0
>        DOGFOOD: 1
> +      MOZHARNESS_CONFIG: b2g/taskcluster-phone-fota.py

where was MOZHARNESS_CONFIG getting set before for these? I tried bubbling up b2g_phone_base.yml to see what config these tasks were passing to build-phone-ota.sh but it doesn't look like we define MOZHARNESS_CONFIG there..
Attachment #8685696 - Flags: review?(jlund) → review+
(Assignee)

Comment 6

2 years ago
(In reply to Jordan Lund (:jlund) from comment #5)
> Comment on attachment 8685696 [details] [diff] [review]
> Enable fota builds for flame and nexus devices. r=jlund
> 
> Review of attachment 8685696 [details] [diff] [review]:
> -----------------------------------------------------------------
> 
> lgmt
> 
> ::: testing/mozharness/configs/b2g/taskcluster-phone-fota.py
> @@ +37,5 @@
> > +    "env": {
> > +        "GAIA_OPTIMIZE": "1",
> > +        "WGET_OPTS": "-c -q"
> > +    },
> > +    "update_types": [ "ota", "fota" ],
> 
> is this the only difference between taskcluster-phone-ota.py and this file?
> If so, we should look into passing update_types via cmd line and sharing the
> config. Shame to have all this duplication.
> 
> ::: testing/taskcluster/tasks/builds/b2g_nexus_5l_ota_debug.yml
> @@ +23,5 @@
> >        B2G_DEBUG: 0
> >        TARGET: 'nexus-5-l'
> >        DEBUG: 0
> >        DOGFOOD: 1
> > +      MOZHARNESS_CONFIG: b2g/taskcluster-phone-fota.py
> 
> where was MOZHARNESS_CONFIG getting set before for these? I tried bubbling
> up b2g_phone_base.yml to see what config these tasks were passing to
> build-phone-ota.sh but it doesn't look like we define MOZHARNESS_CONFIG
> there..

It defaults to taskcluster-phone-ota.py

Comment 7

2 years ago
https://hg.mozilla.org/integration/b2g-inbound/rev/baa579f72288

Comment 8

2 years ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/baa579f72288
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.