Fixes up ESR bouncer aliases now that ESR60 is EOL.
Adds check for latest products used by www.mozilla.org.
Enables the cron checks.
Fixes up a script error which meant we weren't checking all partial platforms in release automation.
Depends on D54656
Differential Revision: https://phabricator.services.mozilla.com/D54657
--HG--
extra : moz-landing-system : lando
I think this is the only mozilla-central patch that is needed at all.
The rest should be just searchfox configuration which I'm testing atm.
Differential Revision: https://phabricator.services.mozilla.com/D48256
--HG--
extra : moz-landing-system : lando
This patch modifies the existing android_power_testing cron task to make it a more general performance testing task that runs a set of tests 3 times a week. The tests that will be running in this task are all chrome, chromium, android CPU+memory, and android power tests.
Differential Revision: https://phabricator.services.mozilla.com/D47140
--HG--
extra : moz-landing-system : lando
Stop running all Raptor tests that run against Fennec. Raptor tests running
against geckoview and geckoview products continues.
Differential Revision: https://phabricator.services.mozilla.com/D44511
--HG--
extra : moz-landing-system : lando
Run fenix and refbrow raptor cold page-load tests once a day, through cron, at 3 AM.
Differential Revision: https://phabricator.services.mozilla.com/D39485
--HG--
extra : moz-landing-system : lando
It turns out there are two places that need to be updated, remove one
of them, and update the other.
Differential Revision: https://phabricator.services.mozilla.com/D36975
--HG--
extra : moz-landing-system : lando
With this patch, all android power tests (idle, idle-bg, and speedometer) will only run once a week, through cron, on saturday.
Differential Revision: https://phabricator.services.mozilla.com/D36827
--HG--
extra : moz-landing-system : lando
Ran locally `./mach taskgraph cron --head-repository=https://hg.mozilla.org/mozilla-central --project=mozilla-central --level=1` and got no errors:
```
0:00.54 using current time for params['time']; try setting $CRON_TIME to a timestamp
0:00.54 calculated cron schedule time is 2019-05-27 09:30:00
0:00.56 not running cron job bouncer-check
0:00.56 not running cron job chromium-update
0:00.56 not running cron job customv8-update
0:00.56 not running cron job nightly-android
0:00.56 not running cron job nightly-desktop
0:00.56 not running cron job nightly-desktop-linux
0:00.56 not running cron job nightly-desktop-osx
0:00.56 not running cron job nightly-desktop-win32
0:00.56 not running cron job nightly-desktop-win64
0:00.56 not running cron job nightly-desktop-win64-aarch64
0:00.56 not running cron job periodic-update
0:00.56 not running cron job pipfile-update
0:00.56 not running cron job searchfox-index
** 0:00.56 not running cron job tp6m-fennec-v64**
```
Feel free to add to this review whoever is relevant.
Differential Revision: https://phabricator.services.mozilla.com/D32674
--HG--
extra : moz-landing-system : lando
This will avoid needing to rebuild the shippable builds are part of nightly
graphs, while we work on nightly promotion.
Differential Revision: https://phabricator.services.mozilla.com/D24968
--HG--
extra : moz-landing-system : lando
We have a cron job to update the chromium, but the tasks were getting optimized
away. Force the target tasks for the cron job to always run.
Differential Revision: https://phabricator.services.mozilla.com/D23380
--HG--
extra : moz-landing-system : lando
This allows the target tasks to include cached tasks, which by default, get
optimized out of the graph on on-`try` branches.
Differential Revision: https://phabricator.services.mozilla.com/D15278
--HG--
extra : moz-landing-system : lando
This patch adds a cron task to regularly schedule an update to the custom d8/v8 version in use in jsshell benchmarks.
Differential Revision: https://phabricator.services.mozilla.com/D15256
--HG--
extra : moz-landing-system : lando
We no longer need a separate nightly task for dmd since it's now enabled by default in nightly m-c builds.
--HG--
extra : rebase_source : d76a27f839055e7af9467f316d5392c269d66112
We shouldn't run this on central, as it falls back to the dev configs, and fails.
It should be fine on beta/release/esr60. I had to move this version of the check to its own
kind to avoid the dependency tree bringing in the entire build process. Perhaps we can
refactor later to avoid duplication
Differential Revision: https://phabricator.services.mozilla.com/D1765
--HG--
rename : taskcluster/ci/release-bouncer-check/kind.yml => taskcluster/ci/bouncer-check/kind.yml
Summary:
the blocklist and remote-settings changes need to happen on beta,
but not the hsts/hpkp updates, so we have to split out the control of what
runs by project.
Reviewers: jlorenzo
Reviewed By: jlorenzo
Bug #: 1436369
Differential Revision: https://phabricator.services.mozilla.com/D1487
--HG--
extra : rebase_source : 19ccbb67b880ee7bd2dc2a37325dd70de635abad
Summary:
I've copied the m-c schedule, as the task sometimes
fails with timeouts. This does add to the releaseduty workload,
until automatic landing is operational.
Reviewers: RyanVM
Reviewed By: RyanVM
Bug #: 1464816
Differential Revision: https://phabricator.services.mozilla.com/D1438
--HG--
extra : rebase_source : 5612fe436d2f44f4d06f21436051256e4052cc43
for: Run buildbot's periodic_file_update job scheduled via taskcluster.
I messed up thinking this was filter-out not filter in the target task method.
I'm also renaming the target_task method in order to avoid these decision jobs
from needing to contact balrog for partial data (because it had 'nightly' in the
target task name.
MozReview-Commit-ID: 3uetnWG4vnW
--HG--
extra : rebase_source : 82dc838d23e02ae2ea515416a29bb0b491c053b9
