Bug 1758746 - Make searchfox run on-push for mozilla-central r=ahal

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
This commit is contained in:
Andrew Sutherland 2022-03-09 21:21:16 +00:00
parent 64907cef51
commit dd464177c0
2 changed files with 18 additions and 25 deletions

View file

@ -29,10 +29,8 @@ jobs:
- mozilla-central
when:
by-project:
# Please update the `searchfox-index` job `mozilla-central` `when`
# times as well if updating the times here.
# `l10n-bumper` job should also have enough time to finish before
# this job runs
# `l10n-bumper` job should have enough time to finish before this
# job runs
mozilla-central: [{hour: 10, minute: 0}, {hour: 22, minute: 0}]
# No default
@ -113,37 +111,32 @@ jobs:
# For more context on this job, see:
# https://github.com/mozsearch/mozsearch-mozilla#how-searchfoxorg-stays-up-to-date
# Note that searchfox now runs on-push for mozilla-central, but continues
# to use cron jobs for all other branches
- name: searchfox-index
job:
type: decision-task
treeherder-symbol: Searchfox
target-tasks-method: searchfox_index
run-on-projects:
- mozilla-central
- mozilla-beta
- mozilla-release
- mozilla-esr91
- elm
# For all non m-c jobs we just run once daily matching the 10 UTC
# nightly which is designed to align with searchfox's AWS cron
# jobs (for legacy reasons) rather than trying to align with
# specific builds. (Ex: mozilla-beta has a "daily-releases" job
# that currently runs 3 times a week.)
#
# Note that for branches that don't change a lot this will result
# in a redundant job being scheduled each day rather than reusing
# the previous day's job. This is only beneficial in the sense
# that there's no risk of expiration for artifacts and is a
# trade-off to avoid stale indices. Bug 1686981 tracks fixing
# this.
when:
by-project:
# We want to run at both of the times the nightly runs.
mozilla-central: [{hour: 10, minute: 0}, {hour: 22, minute: 0}]
# For all other jobs we just run once daily matching the 10 UTC
# nightly which is designed to align with searchfox's AWS cron
# jobs (for legacy reasons) rather than trying to align with
# specific builds. (Ex: mozilla-beta has a "daily-releases" job
# that currently runs 3 times a week.)
#
# Note that for branches that don't change a lot this will result
# in a redundant job being scheduled each day rather than reusing
# the previous day's job. This is only beneficial in the sense
# that there's no risk of expiration for artifacts and is a
# trade-off to avoid stale indices. Bug 1686981 tracks fixing
# this.
mozilla-beta: [{hour: 10, minute: 0}]
mozilla-release: [{hour: 10, minute: 0}]
mozilla-esr91: [{hour: 10, minute: 0}]
elm: [{hour: 10, minute: 0}]
- {hour: 10, minute: 0}
- name: linux64-clang-trunk-perf
job:

View file

@ -22,7 +22,7 @@ job-defaults:
symbol: Searchfox(idx)
kind: build
tier: 2
run-on-projects: []
run-on-projects: ['mozilla-central']
optimization: null
jobs: