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
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
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
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
Updating the HSTS preload list is now taking close to the previous limit
of 5 hours, so bump it to 6 hours as a stopgap, and adjust the start
time to keep its end time from going too late in the day.
Differential Revision: https://phabricator.services.mozilla.com/D112346
1. Add task to get and build clang from the main branch.
2. Using clang main toolchain we build on a daily basis linux64 firefox, this tasks also automatically triggers the fetch and build of clang from main branch since we don't cache it.
Differential Revision: https://phabricator.services.mozilla.com/D111063
I have manually pinned the requirements, and partials are working. We'll lose a way to auto-update our dependencies, but a) it's perma-busted, so realistically we're just losing a busted task, and b) mhentges is working on a way to auto-update pinned dependencies in-tree.
Differential Revision: https://phabricator.services.mozilla.com/D110148
To ensure l10n updates are still picked up by beta builds in a timely
fashion, remove "DONTBUILD" from commit messages when running on
mozilla-beta, and run a couple of hours before the "daily-releases" job
starts.
Differential Revision: https://phabricator.services.mozilla.com/D98349
To ensure l10n updates are still picked up by beta builds in a timely
fashion, remove "DONTBUILD" from commit messages when running on
mozilla-beta, and run a couple of hours before the "daily-releases" job
starts.
Differential Revision: https://phabricator.services.mozilla.com/D98349
