Differential Revision: https://phabricator.services.mozilla.com/D189257

Bug 1836078 - Update gecko taskgraph to support ESR115 r=releng-reviewers,taskgraph-reviewers,jcristau, a=release

Differential Revision: https://phabricator.services.mozilla.com/D180026

Bug 1824829 - Add a daily cron for building and running performance tests on custom-car. r=perftest-reviewers,afinder

This patch adds a daily cron task to build the custom chromium-as-release (CaR) application and running
raptor browsertime tests with it.

Differential Revision: https://phabricator.services.mozilla.com/D177545

Bug 1825574 - Create a daily cron to run Chrome release tests against Speedometer 3 for android and desktop. r=perftest-reviewers,sparky

Differential Revision: https://phabricator.services.mozilla.com/D174163

Differential Revision: https://phabricator.services.mozilla.com/D172444

Bug 1822107 - Run the Beta l10n-bumper job an hour earlier. r=releng-reviewers,jcristau a=release DONTBUILD

Differential Revision: https://phabricator.services.mozilla.com/D172444

Differential Revision: https://phabricator.services.mozilla.com/D172040

Differential Revision: https://phabricator.services.mozilla.com/D170084

Bug 1666491 - Add a eslint-build tester (tier 3) that depends on xpt artifacts. r=nalexander,releng-reviewers,gbrown

Depends on D161641

Differential Revision: https://phabricator.services.mozilla.com/D162072

Differential Revision: https://phabricator.services.mozilla.com/D156972

Bug 1790476 - Add a cron to run browsertime tests weekly on the mozilla-release branch. r=sparky,perftest-reviewers

This patch limits the frequency of performance tests running on the mozilla-release branch. In particular, we need to reduce the load on our android devices for the time being, similar to how we did this for the beta branch in bug 1788026.

Differential Revision: https://phabricator.services.mozilla.com/D157159

Renaming `nightly` to `daily` is intended for avoiding confusion with Nightly builds and better reflect what we are doing with these performance tests.

Differential Revision: https://phabricator.services.mozilla.com/D156324

There will be changes in mozilla-beta that will increase the frequency of pushes. This will increase the load on our android devices so this patch will limit the amount of tests to be run nightly rather than on every push.

Differential Revision: https://phabricator.services.mozilla.com/D156198

Renaming `nightly` to `daily` is intended for avoiding confusion with Nightly builds and better reflect what we are doing with these performance tests.

Differential Revision: https://phabricator.services.mozilla.com/D154305

There will be changes in mozilla-beta that will increase the frequency of pushes. This will increase the load on our android devices so this patch will limit the amount of tests to be run nightly rather than on every push.

Differential Revision: https://phabricator.services.mozilla.com/D156198

Differential Revision: https://phabricator.services.mozilla.com/D154305

Bug 1790476 - Add a cron to run browsertime tests weekly on the mozilla-release branch. r=sparky, a=test-only DONTBUILD

This patch limits the frequency of performance tests running on the mozilla-release branch. In particular, we need to reduce the load on our android devices for the time being, similar to how we did this for the beta branch in bug 1788026.

Differential Revision: https://phabricator.services.mozilla.com/D157159

Differential Revision: https://phabricator.services.mozilla.com/D154305

Backed out changeset 06e2145b5a21 (bug 1752111) for causing linting failures on release_version_bump.py. CLOSED TREE

Differential Revision: https://phabricator.services.mozilla.com/D154305

Differential Revision: https://phabricator.services.mozilla.com/D150369

Bug 1768747 - Disables msix-latest and msix-next-latest uptake check on esr. Enables the esr102 bouncer check in .cron.yml r=jcristau

Differential Revision: https://phabricator.services.mozilla.com/D150767

backfill-all-browsertime cron task had been added in bug 1766433.

Differential Revision: https://phabricator.services.mozilla.com/D146557

This patch adds a cron job that runs daily and triggers the backfill-all-browsertime action task for the revisions containing commits that were reviewed by #perftest for the daay before the job is running.

Differential Revision: https://phabricator.services.mozilla.com/D144713

Differential Revision: https://phabricator.services.mozilla.com/D145900

Differential Revision: https://phabricator.services.mozilla.com/D144574

In order to help ensure that searchfox runs for mozilla-central will
always have code coverage information available, run the searchfox jobs
on-push instead of on a cron schedule.  This avoids searchfox jobs
being scheduled against DONTBUILD pushes which will lack the coverage
jobs which are normally scheduled on-push.

A better/more thorough thing to do would be to express soft
dependencies "soft-dependencies" as documented at
https://taskcluster-taskgraph.readthedocs.io/en/latest/concepts/task-graphs.html#soft-dependencies
on these coverage tasks.  However, for now, we just hope really hard
that the coverage tasks get scheduled (as they should? :).

Differential Revision: https://phabricator.services.mozilla.com/D140675

Differential Revision: https://phabricator.services.mozilla.com/D135947

Differential Revision: https://phabricator.services.mozilla.com/D130178

Differential Revision: https://phabricator.services.mozilla.com/D129779

Differential Revision: https://phabricator.services.mozilla.com/D127433

Differential Revision: https://phabricator.services.mozilla.com/D124988

Differential Revision: https://phabricator.services.mozilla.com/D121087

Differential Revision: https://phabricator.services.mozilla.com/D119521

In Bug 1717600 we introduced the monitoring of performance for ff using clang-trunk toolchain,
we did this for mozilla-central and mozilla-beta, but after analyzing further the problem we
don't have to run it on beta since we can compare the graph of ff built with clang-trunk against
clang official and if the slopes of the two graphs have the same degrees this means that there
is no perf regression caused.

Differential Revision: https://phabricator.services.mozilla.com/D118814

Differential Revision: https://phabricator.services.mozilla.com/D119521