Setups up a new daily cron task to run select UI tests on API 28 (we’ll call it legacy). We don’t necessarily want to invoke Flank twice (serial) with a different configuration (FTL APIs dont support API splitting per test-target) on event CI but we do want them running elsewhere (cron).
Bug 1614763 - [ci] Create beetmover tasks to publish release artifacts
Added TODO
Added head_tag to try_task_config
Change locale to multi and fix beetmover URL destinations
Bump version
Adjust beetmover kind and add beta + format task label
Allow all build types for beetmover
Bump version
Adjust beetmover destination URL + minor mods
Try task config - nightly
Change try release to beta
Remove try_task_config
This was moved to once per day in https://bugzilla.mozilla.org/show_bug.cgi?id=1628413 when Google Play reviews were very slow. That hasn't been a problem for awhile, and the less frequent nightlies are causing delays getting new Android Components bumps shipped out.
* For #19801 - Update to latest version of taskgraph
* For #19801 - Update to latest decision-mobile image
We need to explicitly set the Java version as Java 11 now co-exists in
the decision-mobile image.
* For #19801 - Run decision task with Python 3
Instead of using a timestamp this will synchronize the Nightly version with the version
of Gecko / A-C. So when using 90.0.20210426143115 then the Nightly version will be
90.0a1 - similar to what Firefox desktop uses.
Let's make mozilla-releng/staging-fenix the official staging repository.
By supporting it in the automation, we no longer need to maintain a
staging patchset to test things properly.
This PR builds on [AC##9024][1], and implements setting the Nimbus endpoints from [a secret set at build time][2].
For production use, this requires a secret named `nimbus_url` to be put into CI.
Note: Nimbus is currently behind a feature flag.
If developers wish to use a Nimbus server for local development, you can set the url by adding an entry into local.properties, e.g.:
```
nimbus.remote-settings.url=https://settings.stage.moz4ws.net
```
Without setting server, Nimbus will be able to function, except no experimental definitions will be fetched, and features under experiment will be configured as if not enrolled in the experiment.
[1]: https://github.com/mozilla-mobile/android-components/pull/9024
[2]: https://groups.google.com/a/mozilla.com/g/android-components-team/c/lAGVKQy8aiA/m/rY3uGAwhBAAJ
