gecko-dev/taskcluster/docs
Andrew Halberstadt 14be9536c1 Bug 1523303 - [taskgraph] Define suite "categories" rather than flavours task configs, r=gbrown
Currently we have the concept of a "suite" and a "flavour" in our task
configuration.  Typically, the "suite" refers to the high-level test harness
like "mochitest" or "reftest", whereas the flavour is more specific, e.g
"browser-chrome-instrumentation" or "crashtest". However the line between suite
and flavour is not applied with any semblance of consistency which results in
inconsistent naming throughout the tree.

This patch gets rid of the concept of "flavours" entirely (at least when it
comes to task configuration). A suite is a type of test run, for example:

    - mochitest-plain
    - mochitest-devtools-chrome
    - mochitest-browser-chrome-instrumentation
    - jsreftest
    - reftest
    - firefox-ui-functional-remote
    etc

There is no confusion here between suites and flavours because flavours don't
exist. However, there are a couple of places where we *do* need to know what
"test harness" is used to run a suite. These cases are:

    1. For SCHEDULES moz.build rules
    2. For the desktop_unittest.py mozharness script which takes arguments like
       --mochitest-suite=browser (this is not a compelling use of this information
       and should be refactored to work more like the android_emulator_unittest.py
       script)

So to get this information, this patch introduces a new concept of a "category"
which is the overall "test harness" that runs the suite. For many suites, the
"category" is identical to the suite name. Unlike flavours, "categories" have
no bearing on how we call or refer to the suite.

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

--HG--
extra : moz-landing-system : lando
2019-04-22 20:44:01 +00:00
..
actions.rst Bug 1529948: Fix refernce to mach test-action-callback; r=Callek 2019-02-22 18:05:17 +00:00
attributes.rst Bug 1523303 - [taskgraph] Define suite "categories" rather than flavours task configs, r=gbrown 2019-04-22 20:44:01 +00:00
balrog.rst
caches.rst
cron.rst
docker-images.rst Backed out 5 changesets (bug 1498640, bug 1436037, bug 1497660, bug 1505579) for mass failures on a CLOSED TREE 2018-11-15 07:53:41 +02:00
how-tos.rst Bug 1539242 - Update link to properties to task definitions in taskcluster's how-to documentation. r=dustin DONTBUILD 2019-03-26 12:28:02 +01:00
index.rst
kinds.rst Bug 1427849 - Digitally sign geckodriver binaries on Windows and Linux r=aki 2019-04-23 09:03:22 +00:00
loading.rst
mach.rst
optimization-process.rst Bug 1527895 - Add soft-dependencies to taskgraph, r=ahal,marco,tomprince,dustin 2019-03-04 17:07:34 +00:00
optimization-schedules.rst
optimization.rst
parameters.rst Bug 1534283 - add a 'tasks_for' property; r=tomprince 2019-03-14 20:01:32 +00:00
partials.rst Bug 1492664 - update references in docs; r=froydnj 2018-09-25 19:06:08 +00:00
partner-repacks.rst
pushapk.rst
pushapk.svg
reference.rst
release-promotion-action.rst
release-promotion.rst
signing.rst
taskcluster-config.rst
taskgraph.rst Bug 1527895 - Add soft-dependencies to taskgraph, r=ahal,marco,tomprince,dustin 2019-03-04 17:07:34 +00:00
transforms.rst Bug 1492664 - add {artifact-reference: ..}; r=tomprince 2018-09-25 20:26:55 +00:00
try.rst Bug 1530908 - Use a transform for try --artifact instead of a morph. r=tomprince 2019-03-05 08:52:19 +00:00
versioncontrol.rst Bug 1535011: update versioncontrol.rst r=dustin 2019-03-16 13:38:05 +00:00