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
We should have CI Lint YAML files in the tree.
MozReview-Commit-ID: 758kdSddjJN
--HG--
extra : rebase_source : d538b8400a92d14ab6b397f33327619e885106cc
We should have CI Lint YAML files in the tree.
MozReview-Commit-ID: 758kdSddjJN
--HG--
extra : rebase_source : 8c8d55ea55737a5c2faca9f91478c72296c881b7
We should have CI Lint YAML files in the tree.
MozReview-Commit-ID: 758kdSddjJN
--HG--
extra : rebase_source : f057b0ce281adb67a156235b051a371a252bd22c
for: Land changes to flip windows nightlies on, and to tier 1 on central
MozReview-Commit-ID: 62cpCHbYN5Y
--HG--
extra : rebase_source : cf5dedc1e3b71ca1a723e94c41a0970c34cdebd1
extra : histedit_source : c0c8ca528392649e0b2c32196e176fca9b65067d
Land date changes to support windows nightlies onto central
MozReview-Commit-ID: 6q7XwWTeXwo
--HG--
extra : rebase_source : aa5522dc98dcd1d606021843da3c72b511e92749
This adds the mozconfigs, mozharness configs and taskcluster changes required
to create optimized DMD builds for linux64, win32, win64 and macosx64.
These builds will happen nightly on mozilla-central
We also add support for custom build variants on Windows (or other generic
worker environments).
MozReview-Commit-ID: HrVT9PLSWVx
--HG--
extra : rebase_source : 39ac752a312afe04187728da82a4a7f722634811
This patch removes the nightly code coverage run in favor of simply running the two code coverage builds on every single push to mozilla-central for a more granular view of code coverage over time.
MozReview-Commit-ID: E4Xp5bB19m9
--HG--
extra : rebase_source : 55bbd7c9d678e3d2b149d210b2a4217a62ddf0e1
This commit adds the target_tasks method to trigger nightlies, and the unscheduled cron entry.
MozReview-Commit-ID: ELcZcUGPg2T
--HG--
extra : rebase_source : 4c7093066d4102022a851c34a32f6ff825a5a541
This is needed because we want to keep the nightly start times aligned with Buildbot starts, in order to keep the possibility of drastically different code going out for one platform in a day and not another (e.g. a merge). The reason the change is needed specifically is because UTC of course doesn't follow Daylight Time shifts, and Pacific time just went through one (+1 hour) which brings it closer to UTC by one hour, so in order to keep UTC matching what buildbot uses we subtract 1 hour from the UTC time.
MozReview-Commit-ID: J07lZYJxlOd
--HG--
extra : rebase_source : d5bb2283a5696fd0bc11f781bb43e294b206040e
This requires moving the schema utilities to their own util module.
MozReview-Commit-ID: KR5xSJ9ak5Y
--HG--
extra : rebase_source : 1c1f6bfb6a08deb8c0be4b2b58db02d85aafeb89
This adds `.cron.yml` and a new mach command to interpret it. While
functionality is limited to nightlies right now, there is room to expand to
more diverse periodic tasks. Let your imagination run wild!
MozReview-Commit-ID: KxQkaUbsjQs
--HG--
extra : rebase_source : ddf0a1eadae5a1169c0ead7bcb7b9ce61b255fbf
