Confirm
3,990
edits
Changes
add more notes
Append --cfg developer_config.py
It will clear any hardcoded paths that are used for Release Engineering machinery.
= Extra notes =
The update tests allow to
specify some more options. Please see all the --update-* options of the
"firefox-ui-update --help" command. What you definitely also need is
--update-allow-mar-channel, --update-target-version, and
--update-target-buildid. The latter two are for final checks that Firefox
has been updated to the correct target version. The MAR channel option is
for updating a release build to a beta build, which happens for RC builds on
the beta channel.
Here are the two examples:
1. Ensure that the update has been applied correctly by checking the target
version and build id
> ./firefox-ui-update --installer %Firefox38.0b8% \
> --update-target-version=38.0b9 --update-target-buildid=20150429135941.
Even if the tests pass without those options defined, it does not mean that
the update was successful. You really want to check that Firefox got updated
to the target build.
2. A beta user got updated to a RC build and has to be brought back to a
beta build. Therefore you need --update-allow-mar-channel
Lets say a beta user was on 38.0b9 and got updated to 38.0RC. This RC build
is on the release channel, but beta users have to be brought back to beta
channel. Given that we currently cannot test updates in multiple steps vXb9
> -> RC -> v(X+1)b1, we have to run vXb9 -> RC, and RC -> v(X+1)b1 separately.
Using the RC build as source build only has the release channel active. The
option above can also enable the beta channel via update-settings.ini.
> ./firefox-ui-update --installer %Firefox38.0% --update-target-version=39.0b1
> --update-target-buildid=%whateveritwillbe%
> --update-allow-mar-channel=firefox-mozilla-beta
= Archive - Failure modes =
