You need other changes to schedule these tasks but this patch lays down the ground for it.
--HG--
rename : testing/taskcluster/tasks/tests/fx_unittest_base.yml => testing/taskcluster/tasks/tests/fx_test_base.yml
extra : commitid : 8ZJ2OXFkr4b
extra : rebase_source : 7ab6dec3c7c19b6f9d251913245b6e0e84904468
The Flame device updates have been broken for a while because of updates
starting to be too big. Because of the way applying OTA works, there is
no good solution except switching to applying Gecko/Gaia updates in
recovery mode. This was done in bug 1037056 on the Buildbot instances,
but we need to support this on TaskCluster also.
Foxfood devices are Sony Xperia Z3c devices. We need to be able to push
updates of the Gonk layer to fix some bugs. Those requires changes to
the kernel, to boot partition and to some other assets. Hence we add
support for producing all kind of updates packages we might need on that
device:
- ota, to update just Gecko/Gaia
- fota, to update Gecko/Gaia in recovery mode
- fota:fullimg, to be able to update gonk also
B2G updates can be of multiple types:
- OTA, applied without rebooting the device,
- FOTA with only Gecko/Gaia,
- FOTA with whole system partition files,
- FOTA dumping partitions images.
Each type of updates has its advantages and drawbacks. There is an
extensive documentation maintained on MDN about each and the options:
https://developer.mozilla.org/en-US/Firefox_OS/Building_and_installing_Firefox_OS/Firefox_OS_update_packages
All those updates are being packaged as a MAR file that gets injected
into the classical Firefox update mechanism, submitted to Balrog and
downloaded by the client. The content of the MAR will however depend on
the type of update: an OTA update will packate a Gecko and Gaia set of
files to update those parts; while any FOTA package is just an
update.zip that will get applied in recovery mode on the device.
So one fundamental difference is that OTA will not reboot your device
(just Gecko) while FOTA requires a working recovery mode and will reboot
your device. But OTA needs more system partition space to get applied,
and it can only update files that are within the /system/b2g/ directory.
FOTA on the other hand can update anything since the payload will
contain an update script written in Edify (Android recovery update
scripting language).
For each device we might need to produce several types of updates that
will be pushed to users depending on the context: for some users we want
to push just a Gecko/Gaia update, for some we know that we need to
update more content and thus we need to send some partitions.
Previously, the b2g_build.py script would only allow one kind of update
payload to be produced for each device available: we would need to have
a device "flame-kk-ota" and "flame-kk-fota" just to produce the OTA and
FOTA packages for the same device, thus resulting in a waste of
computing power and storage.
This commit introduces a new field "update_types" that can take an array
of values:
- ota, to produce an OTA package as before
- fota, to produce a FOTA package with only Gecko/Gaia
- fota:full, to produce a FOTA package of all files of the system
partition
- fota:fullimg, to produce a FOTA package dumping partitions
The old "update_type" will be used in the absence of "update_types". And
if none are present, we will keep defaulting to generating OTA as
previously.
Armen Zambrano Gasparnian
Carsten "Tomcat" Book
Johan Lorenzo
Edgar Chen
Dustin J. Mitchell
Wander Lairson Costa
Ronald Claveau
Gregory Arndt
Wes Kocher
Naoki Hirata
Alexandre Lissy
Alexandre Poirot