search

biancadanforth / taskcluster-integration-poc

A proof-of-concept to push to the Try server from GitHub via a Taskcluster job for off-train experiments at Mozilla
Mozilla Public License 2.0
0 stars 0 forks source link

Make which Firefox channel to run CI on configurable #10

Open biancadanforth opened 5 years ago

biancadanforth commented 5 years ago

Currently, we only clone mozilla-central (or mozilla-unified, defaulting to the central branch), but often, experiments are intended for release channels like Beta and Release.

While the hg clone command repo URL can easily be updated for these different repos[1] (or we could also clone the mono-repo mozilla-unified), it is harder to create an artifact build for Beta or Release after that clone, as release artifact builds currently requires adding 'releases/mozilla-beta' or 'releases/mozilla-release' respectively to the list of CANDIDATE_TREES in ./python/mozbuild/mozbuild/artifacts.py.

[1]: Repo URLs:

biancadanforth commented 5 years ago

Note, to run unsigned legacy web extensions (WEEs) on release channels (Release and Beta), this must be added to .mozconfig:

ac_add_options MOZ_ALLOW_LEGACY_EXTENSIONS=1

Note: Just changing the extensions.legacy.enabled pref in Firefox doesn't override this build config (it's ignored due to the build time setting). You can verify that it is true by running AppConstants.MOZ_ALLOW_LEGACY_EXTENSIONS in the browser console. AppConstants.MOZ_REQUIRE_SIGNING also should be false, but the xpinstall.signatures.required pref is sufficient for that.