mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-27 20:25:44 +00:00
ffca84ff7d
This introduces a completely new way of specifying test task in-tree,
completely replacing the old spider-web of YAML files.
The high-level view is this:
- some configuration files are used to determine which test suites to run
for each test platform, and against which build platforms
- each test suite is then represented by a dictionary, and modified by a
sequence of transforms, duplicating as necessary (e.g., chunks), until
it becomes a task definition
The transforms allow sufficient generality to support just about any desired
configuration, with the advantage that common configurations are "easy" while
unusual configurations are supported but notable for their oddness (they
require a custom transform).
As of this commit, this system produces the same set of test graphs as the
existing YAML, modulo:
- extra.treeherder.groupName -- this was not consistent in the YAML
- extra.treeherder.build -- this is ignored by taskcluster-treeherder anyway
- mozharness command argument order
- boolean True values for environment variables are now the string "true"
- metadata -- this is now much more consistent, with task name being the label
Testing of this commit demonstrates that it produces the same set of test tasks for
the following projects (those which had special cases defined in the YAML):
- autoland
- ash (*)
- willow
- mozilla-inbound
- mozilla-central
- try:
-b do -p all -t all -u all
-b d -p linux64,linux64-asan -u reftest -t none
-b d -p linux64,linux64-asan -u reftest[x64] -t none[x64]
(*) this patch omits the linux64/debug tc-M-e10s(dt) test, which is enabled on
ash; ash will require a small changeset to re-enable this test.
IGNORE BAD COMMIT MESSAGES (because the hook flags try syntax!)
MozReview-Commit-ID: G34dg9f17Hq
--HG--
rename : taskcluster/taskgraph/kind/base.py => taskcluster/taskgraph/task/base.py
rename : taskcluster/taskgraph/kind/docker_image.py => taskcluster/taskgraph/task/docker_image.py
rename : taskcluster/taskgraph/kind/legacy.py => taskcluster/taskgraph/task/legacy.py
extra : rebase_source : 03e70902c2d3a297eb9e3ce852f8737c2550d5a6
extra : histedit_source : d4d9f4b192605af21f41d83495fc3c923759c3cb
31 lines
1.0 KiB
ReStructuredText
31 lines
1.0 KiB
ReStructuredText
.. taskcluster_index:
|
|
|
|
TaskCluster Task-Graph Generation
|
|
=================================
|
|
|
|
The ``taskcluster`` directory contains support for defining the graph of tasks
|
|
that must be executed to build and test the Gecko tree. This is more complex
|
|
than you might suppose! This implementation supports:
|
|
|
|
* A huge array of tasks
|
|
* Different behavior for different repositories
|
|
* "Try" pushes, with special means to select a subset of the graph for execution
|
|
* Optimization -- skipping tasks that have already been performed
|
|
* Extremely flexible generation of a variety of tasks using an approach of
|
|
incrementally transforming job descriptions into task definitions.
|
|
|
|
This section of the documentation describes the process in some detail,
|
|
referring to the source where necessary. If you are reading this with a
|
|
particular goal in mind and would rather avoid becoming a task-graph expert,
|
|
check out the :doc:`how-to section <how-tos>`.
|
|
|
|
.. toctree::
|
|
|
|
taskgraph
|
|
parameters
|
|
attributes
|
|
kinds
|
|
transforms
|
|
yaml-templates
|
|
how-tos
|